From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH/obvious] Fix 7.7 branch date annoucement
Date: Fri, 31 Jan 2014 10:24:00 -0000 [thread overview]
Message-ID: <m3sis4e9ed.fsf@redhat.com> (raw)
In-Reply-To: <20140131100348.GX4101@adacore.com> (Joel Brobecker's message of "Fri, 31 Jan 2014 14:03:48 +0400")
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.
> Attached is what I ended up checking in...
Thanks a lot.
--
Sergio
next prev parent reply other threads:[~2014-01-31 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 9:28 Sergio Durigan Junior
2014-01-31 10:03 ` Joel Brobecker
2014-01-31 10:24 ` Sergio Durigan Junior [this message]
2014-01-31 10:39 ` Joel Brobecker
2014-01-31 10:50 ` Sergio Durigan Junior
2014-02-04 19:12 ` Pedro Alves
2014-02-06 11:29 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3sis4e9ed.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox