Stephen Leake wrote:
Ok, that is helpful. Perhaps that file should be mentioned in HACKING;
I would not think to look in Changelog for instructions on writing
commit messages :).
Sure, feel free to add something appropriate. ;)
But after you document the detailed changes to each file, you
Derek Scherger [EMAIL PROTECTED] writes:
Stephen Leake wrote:
I have wondered about the proper format/content for changes in nvm.
I'd appreciate some written guidance in HACKING.
If nothing else the current ChangeLog file does give a bit of info about
this along with saying that it is no
Richard Levitte [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] on Tue, 11 Sep 2007 07:12:54 -0400, Stephen
Leake [EMAIL PROTECTED] said:
stephen_leake On the other hand, that is the way we typically work. I
stephen_leake often notice little things while I'm working on one
On 9/11/07, Nathaniel Smith [EMAIL PROTECTED] wrote:
Just some ideas:
Consider (user-visible) features F and G, implemented both in branch
A. Each feature can easily constituted of multiple changesets, but I
assume for a moment that no single changeset is related to both F and
G at
Stephen Leake wrote:
I have wondered about the proper format/content for changes in nvm.
I'd appreciate some written guidance in HACKING.
If nothing else the current ChangeLog file does give a bit of info about
this along with saying that it is no longer used.
I'm with Zack on the value
On Sep 11, 2007, at 2:18 AM, William Uther wrote:
On 10/09/2007, at 7:49 PM, Thomas Keller wrote:
Hi all!
I've noticed that the changelog some people use for monotone is not
quite GNU-style. I'm sure you all hacked stuff longer than me,
so you
can correct me at any time, but aren't we
In message [EMAIL PROTECTED] on Tue, 11 Sep 2007 12:22:43 +0200, Julio M.
Merino Vidal [EMAIL PROTECTED] said:
jmmv84 Using plain text messages will make one think twice before
jmmv84 doing that, because he'll have to explain *why* he is
jmmv84 committing that at once.
I totally agree with
Richard Levitte [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] on Tue, 11 Sep 2007 12:22:43 +0200, Julio M.
Merino Vidal [EMAIL PROTECTED] said:
jmmv84 Using plain text messages will make one think twice before
jmmv84 doing that, because he'll have to explain *why* he is
jmmv84
On Sep 11, 2007, at 1:12 PM, Stephen Leake wrote:
Richard Levitte [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] on
Tue, 11 Sep 2007 12:22:43 +0200, Julio M. Merino Vidal
[EMAIL PROTECTED] said:
jmmv84 Using plain text messages will make one think twice before
jmmv84 doing that,
In message [EMAIL PROTECTED] on Tue, 11 Sep 2007 07:12:54 -0400, Stephen
Leake [EMAIL PROTECTED] said:
stephen_leake On the other hand, that is the way we typically work. I
stephen_leake often notice little things while I'm working on one
stephen_leake big thing. Would it be better to _not_ fix
On 9/11/07, Richard Levitte [EMAIL PROTECTED] wrote:
You're talking about two different kinds of documentations. When I
update my workspace, or even better, when I'm about to, and I want to
know what will happen, the most natural is to check out the log. If
all the log says is that this and
On Tue, Sep 11, 2007 at 10:00:49AM -0500, Hugo Cornelis wrote:
Using certs, it is possible to link sets of revisions to an entry in
an external log file. Then each entry in the external log file can
contain a global description of what happened for this set of
revisions.
That way, and with
On 9/11/07, Nathaniel Smith [EMAIL PROTECTED] wrote:
On Tue, Sep 11, 2007 at 10:00:49AM -0500, Hugo Cornelis wrote:
Using certs, it is possible to link sets of revisions to an entry in
an external log file. Then each entry in the external log file can
contain a global description of what
On Tue, Sep 11, 2007 at 11:57:34AM -0500, Hugo Cornelis wrote:
On 9/11/07, Nathaniel Smith [EMAIL PROTECTED] wrote:
I propose that set of revisions ~ branch? It would definitely be
nice to have more branch metadata.
Yes, there is a relationship between them, I am not sure what you mean
On 9/11/07, Richard Levitte [EMAIL PROTECTED] wrote:
You're talking about two different kinds of documentations. When I
update my workspace, or even better, when I'm about to, and I want to
know what will happen, the most natural is to check out the log. If
all the log says is that this and
On 11/09/2007, at 9:12 PM, Stephen Leake wrote:
Richard Levitte [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] on
Tue, 11 Sep 2007 12:22:43 +0200, Julio M. Merino Vidal
[EMAIL PROTECTED] said:
jmmv84 Using plain text messages will make one think twice before
jmmv84 doing that,
On 10/09/2007, at 7:49 PM, Thomas Keller wrote:
Hi all!
I've noticed that the changelog some people use for monotone is not
quite GNU-style. I'm sure you all hacked stuff longer than me, so
you
can correct me at any time, but aren't we forced to use some kind of
GNU-style syntax to make
17 matches
Mail list logo
