Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod)
Date: Sat, 24 Dec 2005 08:07:00 -0000	[thread overview]
Message-ID: <ubqz7irdd.fsf@gnu.org> (raw)
In-Reply-To: <u3bkr7353.fsf@gnu.org> (message from Eli Zaretskii on Sun, 18 	Dec 2005 00:46:48 +0200)

> Date: Sun, 18 Dec 2005 00:46:48 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > IMO we really should do them all at once.  The other thing we need to
> > do is update the FSF address; I have had this flagged to take care of
> > since the FSF moved this spring, but I (obviously) haven't found the
> > time...
> 
> I've committed the first portion of this monstrous job: all the files
> in gdb/ and in gdb/cli/ now have the (c) marker and state the correct
> FSF address.  I hope I didn't break anything, but if I did, please
> correct as obvious.

I now did that for gdb/gdbserver, gdbtk/generic, and gdbtk/library.

But I inadvertently hit a snafu in the image subdirectories of
gdbtk/library: due to mismatch of time stamp (it's a long story) and
my failure to use "cvs ci -l", CVS checked in various GIF and PNG
images as well.  The problem is, these are binary files, but they are
not marked with -kb keyword in the repository.  And because I did the
commit from a Windows machine, I'm afraid the files are now corrupted
in the repository.

Could someone please undo my commits to image files in all the
subdirectories of gdbtk/library?  I'd do that myself, but in order to
be able to do that, I need to be a member of the cvsadmin group, which
I apparently am not...

Sorry for the inconvenience.


  parent reply	other threads:[~2005-12-23 18:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 22:46 [RFC] fix testsuite/gdb.cp/printmethod Christophe LYON
2005-12-08  9:48 ` Daniel Jacobowitz
2005-12-08 18:37   ` Eli Zaretskii
2005-12-08 19:22     ` Daniel Jacobowitz
2005-12-09  2:12       ` Jim Blandy
2005-12-09  2:25       ` Eli Zaretskii
2005-12-19 22:39       ` Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod) Eli Zaretskii
2005-12-20  3:04         ` Daniel Jacobowitz
2005-12-20 14:19           ` Daniel Jacobowitz
2005-12-20  3:18         ` Mark Kettenis
2005-12-24  8:07         ` Eli Zaretskii [this message]
2005-12-24  8:57           ` Update Copyright and FSF address Eli Zaretskii
2005-12-24 10:50           ` Update Copyright and FSF address (was: [RFC] fix testsuite/gdb.cp/printmethod) Daniel Jacobowitz
2005-12-24 17:37             ` Eli Zaretskii
2005-12-26 14:39               ` Eli Zaretskii
2005-12-26 19:15               ` Daniel Jacobowitz
2005-12-26 19:31                 ` Eli Zaretskii
2005-12-27  4:09                   ` Daniel Jacobowitz
2005-12-27 12:23                     ` Eli Zaretskii
2005-12-09  8:05     ` [RFC] fix testsuite/gdb.cp/printmethod Mark Kettenis
2005-12-09 18:51   ` Christophe LYON

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=ubqz7irdd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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