All of lore.kernel.org
 help / color / mirror / Atom feed
From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gdb
Date: Wed, 26 Sep 2007 07:16:49 -0700 (PDT)	[thread overview]
Message-ID: <20070926141649.8726830063@busybox.net> (raw)

Author: aldot
Date: 2007-09-26 07:16:47 -0700 (Wed, 26 Sep 2007)
New Revision: 20040

Log:
- sjhill?


Modified:
   trunk/buildroot/toolchain/gdb/Config.in.2


Changeset:
Modified: trunk/buildroot/toolchain/gdb/Config.in.2
===================================================================
--- trunk/buildroot/toolchain/gdb/Config.in.2	2007-09-26 12:18:07 UTC (rev 20039)
+++ trunk/buildroot/toolchain/gdb/Config.in.2	2007-09-26 14:16:47 UTC (rev 20040)
@@ -1,4 +1,5 @@
 # Keep this in sync with Config.in
+# Why don't you use Config.in in the first place?
 
 comment "Gdb Options"
 

             reply	other threads:[~2007-09-26 14:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 14:16 aldot at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-08  8:54 [Buildroot] svn commit: trunk/buildroot/toolchain/gdb jacmet at uclibc.org
2008-12-08  8:46 jacmet at uclibc.org
2008-12-08  8:46 jacmet at uclibc.org
2008-12-07 21:22 jacmet at uclibc.org
2008-08-24  7:48 jacmet at uclibc.org
2008-07-01 21:46 ulf at uclibc.org
2008-07-01 21:38 ulf at uclibc.org
2008-07-01 21:36 ulf at uclibc.org
2008-06-16 15:52 jacmet at uclibc.org
2008-02-07 10:59 vanokuten at uclibc.org
2008-02-08  9:07 ` Atle Nissestad
2008-02-08 10:45   ` Ivan Kuten
2007-07-29 17:34 ulf at uclibc.org
2007-06-26 14:32 aldot at uclibc.org
2007-06-22 10:42 aldot at uclibc.org
2007-06-16 17:55 sjhill at uclibc.org

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=20070926141649.8726830063@busybox.net \
    --to=aldot@uclibc.org \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.