El 08/09/2011 19:22, "David Kastrup" escribió:
>
> Francisco Vila writes:
>
> >> d) "Translation of GIT committish: xxx". Uh. What to put into
> >> "committish"? Likely the merge commit.
> >
> > Or the last commit in the history of the original file which this is
> > a translation of. It is w
Graham Percival writes:
> On Thu, Sep 08, 2011 at 04:12:04PM +0200, David Kastrup wrote:
>>
>> Well, I tried pushing a multi-commit change as a single merge commit
>> right now.
>
> Thanks for the experiment! This is useful information for a
> long-away GOP proposal
> http://lilypond.org/~graha
2011/9/8 David Kastrup :
>
> Well, I tried pushing a multi-commit change as a single merge commit
> right now. The idea behind this was that the last commit in the
> sequence was getting most of the testing attention, and usually nobody
> will gain from bisecting possibly suboptimal commits in the
On Thu, Sep 08, 2011 at 04:12:04PM +0200, David Kastrup wrote:
>
> Well, I tried pushing a multi-commit change as a single merge commit
> right now.
Thanks for the experiment! This is useful information for a
long-away GOP proposal
http://lilypond.org/~graham/gop/gop_19.html
(currently "GOP h -
Francisco Vila writes:
>> d) "Translation of GIT committish: xxx". Uh. What to put into
>> "committish"? Likely the merge commit.
>
> Or the last commit in the history of the original file which this is
> a translation of. It is well known by looking at the fisrt line of git
> log the_fil
> d) "Translation of GIT committish: xxx". Uh. What to put into
> "committish"? Likely the merge commit.
Or the last commit in the history of the original file which this is a
translation of. It is well known by looking at the fisrt line of git log
the_file.
_
Well, I tried pushing a multi-commit change as a single merge commit
right now. The idea behind this was that the last commit in the
sequence was getting most of the testing attention, and usually nobody
will gain from bisecting possibly suboptimal commits in the sequence (I
did try to make reaso
