Re: Proposal to deploy GitLab on gnome.org
- From: Sébastien Wilmet <swilmet gnome org>
- To: Tobias Mueller <muelli cryptobitch de>
- Cc: Zbigniew Jędrzejewski-Szmek <zbyszek in waw pl>, desktop-devel-list gnome org
- Subject: Re: Proposal to deploy GitLab on gnome.org
- Date: Mon, 25 Sep 2017 22:03:27 +0200
On Mon, Sep 25, 2017 at 09:03:00PM +0200, Tobias Mueller wrote:
On Mi, 2017-05-17 at 14:21 +0000, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, May 17, 2017 at 01:49:21PM +0200, Sébastien Wilmet wrote:
By attaching a patch to a bugtracker ticket, we loose the information of
the parent commit: where the commit has been initially created in the
git history.
If the patch is created by git format-patch, it contains the hash of
the parent, so git knows the original parent
I couldn't find the hash of the parent commit in my git format-patch
exported patch, e.g. https://bug778584.bugzilla-attachments.gnome.org/a
ttachment.cgi?id=345698.
Do I need to do anything special in order to export the parent also?
The man page for git-format-patch does not show anything useful for
"parent".
It contains the hashes of the parent *objects*: typically it refers to
the last time that the file was modified.
But a patch often depends on more recent changes made in *other* files,
for example when calling a function of another class that was recently
implemented or changed.
So there is a loss of information when creating a patch with git
format-patch, at least with the default parameters.
--
Sébastien
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]