This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH/obvious] Fix 7.7 branch date annoucement
- From: Pedro Alves <palves at redhat dot com>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, GDB Patches <gdb-patches at sourceware dot org>
- Date: Tue, 04 Feb 2014 19:12:46 +0000
- Subject: Re: [PATCH/obvious] Fix 7.7 branch date annoucement
- Authentication-results: sourceware.org; auth=none
- References: <m34n4kfqkr dot fsf at redhat dot com> <20140131100348 dot GX4101 at adacore dot com> <m3sis4e9ed dot fsf at redhat dot com>
On 01/31/2014 10:24 AM, Sergio Durigan Junior wrote:
> On Friday, January 31 2014, Joel Brobecker wrote:
>
>> Hi Sergio,
>
> Hey Joel,
>
>>> We've received a notice on the GNU GDB ml mentioning that the GDB 7.7
>>> branch date annoucement in our website is wrong (s/2013/2014). I cloned
>>> the repository and fixed this (here's the patch), but I'm not sure if I
>>> can just go ahead and check it in, or if there's some other thing I need
>>> to do.
>>>
>>> Anyway, here's the patch. I can check it in if you give me a green
>>> light.
>>
>> Thanks for the fix. In my initial reply, I had given you the green
>> light, with the following blurb: Make sure that you commit the patch
>> both to savannah (which feeds the side on gnu.org) and to the htdocs
>> repository at sourceware.org:/cvs/gdb (which feeds the sourceware.org
>> mirror). I usually have one single git mirror inside which I make
>> the changes, which I then cvsexportcommit to both CVS repositories.
>
> Hm, I went to <https://sourceware.org/gdb/current/> and cloned "cvs -d
> :ext:YOURACCOUNT@sourceware.org:/cvs/gdb co htdocs", but the repo was
> empty. Not sure if I made something wrong...
>
>> In this case, I went ahead because I also noticed that the "Last
>> Updated" timestamps had not been updated. YOu need to run the index.sh
>> script on all HTML files updated....
>
> Aha, nice, thanks for the instructions.
I wonder whether this process is recorded/documented somewhere? The
wiki perhaps? That'd be great, so next time we could just point
people at an URL.
--
Pedro Alves