Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Re: missing commit details (was Re: [Kea-changes] KEA
trac3824, updated. 7697c53c441338748fd678e10c3b38384f379ef6
[3824] #3824 patches) (Francis Dupont)
2. Re: missing commit details (was Re: [Kea-changes] KEA
trac3824, updated. 7697c53c441338748fd678e10c3b38384f379ef6
[3824] #3824 patches) (Francis Dupont)
----------------------------------------------------------------------
Message: 1
Date: Tue, 12 May 2015 14:47:31 +0000
From: Francis Dupont <[email protected]>
To: "Jeremy C. Reed" <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] missing commit details (was Re: [Kea-changes]
KEA trac3824, updated.
7697c53c441338748fd678e10c3b38384f379ef6 [3824]
#3824 patches)
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
"Jeremy C. Reed" writes:
> On Tue, 12 May 2015, [email protected] wrote:
>
> > [3824] #3824 patches
=> I can't see what is the problem: you have the branch tag and
a comment giving the reference to what are in patches (is in the patch
for the few others)... Unfortunately the script didn't copy the
subject of the ticket, perhaps it is your concern.
> I saw multiple branches with similar commit log messages. Please
> consider some details in future. (I cannot find in the instructions for
> this in the trac wiki.)
=> GitTips (http://kea.isc.org/wiki/GitTips). Note I applied them
(with some debugs) as you have the tag name '[3824]'.
Regards
Francis Dupont <[email protected]>
------------------------------
Message: 2
Date: Tue, 12 May 2015 15:02:09 +0000
From: Francis Dupont <[email protected]>
To: Thomas Markwalder <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] missing commit details (was Re: [Kea-changes]
KEA trac3824, updated.
7697c53c441338748fd678e10c3b38384f379ef6 [3824]
#3824 patches)
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Be cool. The uniq role of the branch is to contain the patch described
in the ticket so anyway the info is to be lost if it will stay there.
Fortunately the next step is to review and merge the patch and at this
time the info will be in the master branch log and perhaps in the
Changelog too...
Regards
Francis Dupont <[email protected]>
Thomas Markwalder writes:
> Nothing is more irritating then commits with no meaningful information.
=> my concern is more about the fact it is not possible to create
a branch with a short explanation of what the branch is for
(in fact perhaps it is possible, cf the --edit-description of git-branch?
but I never saw it to be used, and it is not of course in the procedures).
------------------------------
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
End of kea-dev Digest, Vol 14, Issue 4
**************************************
