[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: openldap.git branch master updated. cf49e43f86de16f1cc84ab44f6d4fa3c7e18902f

To: Kurt Zeilenga <kurt@openldap.org>
Subject: Re: openldap.git branch master updated. cf49e43f86de16f1cc84ab44f6d4fa3c7e18902f
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Tue, 29 Mar 2011 16:44:47 +0200
Cc: openldap-commit2devel@openldap.org
In-reply-to: <0BA8D32C-2751-427D-B249-469BBBB00DC9@openldap.org>
References: <hbf.20110329kxmj@bombur.uio.no> <0BA8D32C-2751-427D-B249-469BBBB00DC9@openldap.org>

Kurt Zeilenga writes:
> I'm not sure why his merge was needed.  Likely I goofed.  I think it
> was a no-op.

Ah.  Well, we'll have more glitches I'm sure.

'gitk --all' or 'git log --graph' shows you did 'Update guide
Copyright/License handling' in one branch and 'Update configure' +
Update for git' in another.  I.e. didn't pull the first before
committing/pushing the second.

-- 
Hallvard

Follow-Ups:
- Re: openldap.git branch master updated. cf49e43f86de16f1cc84ab44f6d4fa3c7e18902f
  - From: Kurt Zeilenga <kurt@OpenLDAP.org>

References:
- Re: openldap.git branch master updated. cf49e43f86de16f1cc84ab44f6d4fa3c7e18902f
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: openldap.git branch master updated. cf49e43f86de16f1cc84ab44f6d4fa3c7e18902f
  - From: Kurt Zeilenga <kurt@OpenLDAP.org>

Prev by Date: Re: openldap.git branch master updated. cf49e43f86de16f1cc84ab44f6d4fa3c7e18902f
Next by Date: Re: openldap.git branch master updated. cf49e43f86de16f1cc84ab44f6d4fa3c7e18902f
Index(es):
- Chronological
- Thread