After testing with a few other options, I come back
to the old method of attaching a git format-patch
formatted file to the message, and adding some intial
comments. So that it would also make it easier to specify
in the subject what repository the patch should be applied.
Another option
I think it would be better to restore the definition of FamilyKrb5Principal
to libXau - while it may not be used by the current code, it is
defined/reserved for Kerberos5 and if a new implementation of that code
was done using current API's, we'd presumably want to use the same family
id for it.
Alan Coopersmith wrote:
I think it would be better to restore the definition of
FamilyKrb5Principal
to libXau - while it may not be used by the current code, it is
defined/reserved for Kerberos5 and if a new implementation of that code
was done using current API's, we'd presumably want to use
On Wed, Feb 04, 2009 at 05:07:26PM -0200, Paulo César Pereira de Andrade wrote:
After testing with a few other options, I come back
to the old method of attaching a git format-patch
formatted file to the message, and adding some intial
comments. So that it would also make it easier to
Ian Romanick wrote:
On Wed, Feb 04, 2009 at 05:07:26PM -0200, Paulo César Pereira de Andrade
wrote:
After testing with a few other options, I come back
to the old method of attaching a git format-patch
formatted file to the message, and adding some intial
comments. So that it would also
