Alessandro Di Marco writes:
> Junio C Hamano writes:
>
>> More importantly, adding non-essential stuff left and right will force
>> third party Git reimplementations to pay attention to them and also
>> will leave room for them to make mistakes when deciding what to
>> propagate, what to drop an
Junio C Hamano writes:
> Ævar Arnfjörð Bjarmason writes:
>> We've already told clients for a long time to ignore fields they
>> don't know about,
> Yes, but the reason that mechanism is there is not because we want to
> add random cruft Git does not have to know about. It is to avoid
> older
Ævar Arnfjörð Bjarmason writes:
> On Mon, Feb 9, 2015 at 2:24 AM, Junio C Hamano wrote:
>> In case I was not clear, I do not think it is likely for us to accept
>> a patch that mucks with object header fields with this information.
>> Have them in the log text and let UI interpret them.
>
> We'v
On Mon, Feb 9, 2015 at 2:24 AM, Junio C Hamano wrote:
> In case I was not clear, I do not think it is likely for us to accept
> a patch that mucks with object header fields with this information.
> Have them in the log text and let UI interpret them.
We've already told clients for a long time to
In case I was not clear, I do not think it is likely for us to accept
a patch that mucks with object header fields with this information.
Have them in the log text and let UI interpret them.
On Sun, Feb 8, 2015 at 4:03 PM, Alessandro Di Marco wrote:
> Junio C Hamano writes:
>
>> I would personal
Junio C Hamano writes:
> I would personally find the "feature" cute, but
> Wouldn't it be sufficient to treat this in a similar way as
> references to tracker entries and references to other commit objects
> in the text of the commit message body are treated by gitk and
> friends? Just embed
Antoine Pelisse writes:
> I'm really not convinced this kind of changes should make it into
> Junio's tree (of course, he's the only one to decide). I really
> believe this is a very specific solution to a very specific problem
> (that is not for me to judge if the problem is real). Bloating the
Antoine Pelisse writes:
On Thu, May 23, 2013 at 10:45 AM, Ramkumar Ramachandra
wrote:
> Alessandro Di Marco wrote:
>> this is a hack I made a couple of years ago in order to store my current
>> location in git commits (I travel a lot and being able to associate a
>> place with
On Thu, May 23, 2013 at 10:45 AM, Ramkumar Ramachandra
wrote:
> Alessandro Di Marco wrote:
>> this is a hack I made a couple of years ago in order to store my current
>> location in git commits (I travel a lot and being able to associate a
>> place with the commit date helps me to quickly recover
Alessandro Di Marco wrote:
> this is a hack I made a couple of years ago in order to store my current
> location in git commits (I travel a lot and being able to associate a
> place with the commit date helps me to quickly recover what were doing
> at that time). Long story short, the screeenshot a
Hi all,
this is a hack I made a couple of years ago in order to store my current
location in git commits (I travel a lot and being able to associate a
place with the commit date helps me to quickly recover what were doing
at that time). Long story short, the screeenshot at
http://tinypic.com/r/war
11 matches
Mail list logo
