This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Fix BZ #14602 ChangeLog entry
- From: Tom de Vries <Tom_deVries at mentor dot com>
- To: Carlos O'Donell <carlos at systemhalted dot org>
- Cc: "H.J. Lu" <hjl dot tools at gmail dot com>, <libc-help at sourceware dot org>
- Date: Mon, 11 Feb 2013 15:17:20 +0100
- Subject: Re: Fix BZ #14602 ChangeLog entry
- References: <5118CCB6.7060806@mentor.com> <CAE2sS1hH7J=P2=EU6TaO+re9HdKO5kuYtVditA6PHnyXvP83xg@mail.gmail.com>
On 11/02/13 14:12, Carlos O'Donell wrote:
> On Mon, Feb 11, 2013 at 5:49 AM, Tom de Vries <Tom_deVries@mentor.com> wrote:
>> Hi,
>>
>> attached patch fixes a typo in this ChangeLog entry:
>> I didn't find a description of how to submit a patch fixing a ChangeLog entry,
>> and couldn't find a ChangeLog entry describing a fix to a ChangeLog entry, so I
>> haven't included a ChangeLog.
>>
>> If this is ok, could you commit this?
>
> Tom,
>
> Can you check it in yourself? :-)
>
> It falls under the trivial rules of community consensus:
> http://sourceware.org/glibc/wiki/Consensus
>
Carlos,
[ moving thread to libc-help ]
By googling I found http://sourceware.org/glibc/wiki/GlibcGit, and checked out
the sources using 'git clone ssh://vries@sourceware.org/git/glibc.git', and set
my user.name and user.email.
But pushing upstream doesn't work for me, I don't seem to have the correct
permissions:
...
$ patch -p1 < ../../upstream/glibc/glibc/fix-log-entry-14602.patch
patching file ChangeLog
$ git add ChangeLog
$ git commit
[master 046f153] Fix typo in ChangeLog entry for commit
03759f47db62930f2dddf1c9733ef89b9d99e2da
1 files changed, 1 insertions(+), 1 deletions(-)
$ git push
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 382 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)
error: insufficient permission for adding an object to repository database ./objects
fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To ssh://vries@sourceware.org/git/glibc.git
! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'ssh://vries@sourceware.org/git/glibc.git'
...
Do I need write approval from overseers@sourceware.org first, or am I doing
something wrong otherwise?
Thanks,
- Tom
> Cheers,
> Carlos.
>