Jeff Hostetler writes:
>> How do you know when a guid needs adaption?
>
> I'm not sure I know what you mean by "adaption".
I think he meant adapting, and I think he is referring to what I
wrote in the message upthread to explain why "file ID" would not
help.
It seems to me, from reading the rem
Stefan Beller writes:
> I have rethought about the idea of GUIDs as proposed by Jeff and wanted
> to give a reply. After rereading this message, I think my thoughts are
> already included via:
>
> - you're doing the work at the wrong point for _another_ reason. You're
> freezing your (crap
On 10/2/2017 3:18 PM, Stefan Beller wrote:
On Mon, Oct 2, 2017 at 11:51 AM, Jeff Hostetler wrote:
Sorry to re-re-...-re-stir up such an old topic.
I wasn't really thinking about commit-to-commit hints.
I think these have lots of problems. (If commit A->B does
"t/* -> tests/*" and commit B-
On Mon, Oct 2, 2017 at 11:51 AM, Jeff Hostetler wrote:
> Sorry to re-re-...-re-stir up such an old topic.
>
> I wasn't really thinking about commit-to-commit hints.
> I think these have lots of problems. (If commit A->B does
> "t/* -> tests/*" and commit B->C does "test/*.c -> xyx/*",
> then you
On 10/2/2017 1:41 PM, Stefan Beller wrote:
It would be nice if every file (and tree) had a permanent GUID
associated with it. Then the filename/pathname becomes a property
of the GUIDs. Then you can exactly know about moves/renames with
minimal effort (and no guessing).
...
https://publi
>> It would be nice if every file (and tree) had a permanent GUID
>> associated with it. Then the filename/pathname becomes a property
>> of the GUIDs. Then you can exactly know about moves/renames with
>> minimal effort (and no guessing).
>
...
> https://public-inbox.org/git/pine.lnx.4.58.05041
Jeff Hostetler writes:
> On 9/29/2017 7:12 PM, Johannes Schindelin wrote:
>
>> Therefore, it would be good to have a way to tell Git about renames
>> explicitly so that it does not even need to use its heuristics.
>
> Agreed.
>
> It would be nice if every file (and tree) had a permanent GUID
> as
Hi Jeff,
On Sat, 30 Sep 2017, Jeff Hostetler wrote:
> On 9/29/2017 7:12 PM, Johannes Schindelin wrote:
>
> > Therefore, it would be good to have a way to tell Git about renames
> > explicitly so that it does not even need to use its heuristics.
>
> Agreed.
>
> It would be nice if every file (an
On 9/29/2017 7:12 PM, Johannes Schindelin wrote:
Hi Philip,
On Fri, 15 Sep 2017, Philip Oakley wrote:
From: "Johannes Schindelin"
In light of such experiences, I have to admit that the notion that the
rename detection can always be improved in hindsight puts quite a bit of
insult to injur
Hi Philip,
On Fri, 15 Sep 2017, Philip Oakley wrote:
> From: "Johannes Schindelin"
>
> > In light of such experiences, I have to admit that the notion that the
> > rename detection can always be improved in hindsight puts quite a bit of
> > insult to injury for those developers who are bitten by
From: "Johannes Schindelin"
Hi Philip,
On Mon, 11 Sep 2017, Philip Oakley wrote:
From: "Pavel Kretov"
> Hi all,
>
> Excuse me if the topic I'm going to raise here has been already
> discussed
> on the mailing list, forums, or IRC, but I couldn't find anything
> related.
>
>
> The problem:
Hi Philip,
On Mon, 11 Sep 2017, Philip Oakley wrote:
> From: "Pavel Kretov"
> > Hi all,
> >
> > Excuse me if the topic I'm going to raise here has been already discussed
> > on the mailing list, forums, or IRC, but I couldn't find anything related.
> >
> >
> > The problem:
> >
> > Git, being "a
From: "Pavel Kretov"
Hi all,
Excuse me if the topic I'm going to raise here has been already discussed
on the mailing list, forums, or IRC, but I couldn't find anything related.
The problem:
Git, being "a stupid content tracker", doesn't try to keep an eye on
operations which happens to indi
Hi Pavel,
On 11/09/2017 09:11, Pavel Kretov wrote:
> Hi all,
>
> Excuse me if the topic I'm going to raise here has been already discussed
> on the mailing list, forums, or IRC, but I couldn't find anything related.
>
>
> The problem:
>
> Git, being "a stupid content tracker", doesn't try to k
On Mon, Sep 11, 2017 at 11:11 AM, Stefan Beller wrote:
> On Mon, Sep 11, 2017 at 12:11 AM, Pavel Kretov wrote:
>> Hi all,
>>
>> Excuse me if the topic I'm going to raise here has been already discussed
>> on the mailing list, forums, or IRC, but I couldn't find anything related.
>>
>>
>> The prob
On Mon, Sep 11, 2017 at 10:11:31AM +0300, Pavel Kretov wrote:
> Unfortunately, the heuristic can only deal with simple file renames with
> no substantial content changes; it's helpless when you:
>
> - rename file and change it's content significantly;
> - split single file into several files;
>
On Mon, Sep 11, 2017 at 12:11 AM, Pavel Kretov wrote:
> Hi all,
>
> Excuse me if the topic I'm going to raise here has been already discussed
> on the mailing list, forums, or IRC, but I couldn't find anything related.
>
>
> The problem:
>
> Git, being "a stupid content tracker", doesn't try to ke
Hi all,
Excuse me if the topic I'm going to raise here has been already discussed
on the mailing list, forums, or IRC, but I couldn't find anything related.
The problem:
Git, being "a stupid content tracker", doesn't try to keep an eye on
operations which happens to individual files; things lik
18 matches
Mail list logo
