[SSSD] [PATCH] COMMON Fixes to return values, errno, leaks

Stephen Gallagher sgallagh at redhat.com
Fri Aug 21 13:09:18 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/21/2009 09:04 AM, Dmitri Pal wrote:
> Stephen Gallagher wrote:
>> On 08/20/2009 06:03 PM, Dmitri Pal wrote:
>>> Steve,
>>
>>> I re-based my source  and used the commit value of
>>> 93c02400b6075f0a4784e87229102bf751f27815 in the tickets but when I tried
>>> to follow the automatically created link the track complained that the
>>> commit doe not exist. Is this Ok?
>>> Some synch delay?
>>
>> No, you used the wrong commit id. The correct one is:
>> 1069fb127a38d875d0ca2f56bfc936a97a964380
>>
>> Sometimes they change when they're pushed to master because they might
>> have required trivial (or non-trivial) merges based on the order they
>> were applied. You should always check gitweb at
>> http://git.fedorahosted.org/git/sssd.git for the correct commit id once
>> it's pushed.
> 
> But when I rebase it should have updated in my git, right?
> 

It should, yes. I'm not sure why it wouldn't have. In any case, always
use the gitweb as the authoritative source for that information.

- -- 
Stephen Gallagher
RHCE 804006346421761

Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkqOnH4ACgkQeiVVYja6o6OjXgCeLGMX20gI9fCukuEoOD+bS+JG
spkAoLD+1e0u2ep/22mepaqJTZBjr3/4
=35ba
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list