octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sharing the savannah hg archive (was: Re: Savannah server unreliable


From: John W. Eaton
Subject: Re: Sharing the savannah hg archive (was: Re: Savannah server unreliable?)
Date: Thu, 11 Sep 2008 16:27:11 -0400

On 11-Sep-2008, Jaroslav Hajek wrote:

| On Thu, Sep 11, 2008 at 7:55 PM, Jaroslav Hajek <address@hidden> wrote:
| 
| > I think it updates the date when transplanting. Not sure about mq.
| > Perhaps it can be configured in some way, or is it a bug? I reckon
| > that when you commit a mq-managed changeset (using hg rm), its date
| > should be updated.
| 
| Okay, it seems I was wrong. The date of the original changeset is also
| preserved. After all, it's little wonder since if it was the other way
| around, then Mercurial should maybe update the dates also when pulling
| or cloning. In other words, it seems Mercurial treats the changeset
| dates in the same way I treat dates in ChangeLog entries - they're
| just an immutable part of the patch.

Are both dates available in the mercurial archive?  Where do they
appear?  A simple "hg log" for the release-3-0-x archive shows:

  changeset:   7574:d92e612d5fe3
  tag:         tip
  user:        Kim Hansen
  date:        Tue May 20 16:49:02 2008 -0400
  summary:     load-path.cc (load_path::initialize): include separator when 
appending sys_path

for example.  It seems to me that it might be helpful to have both
dates, at least when cherrypicking changes from another archive.

But anyway, what about the idea of simply dropping the formal
ChangeLog?  Or perhaps only auto-generating them from the Mercurial
commit logs when we make releases?

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]