All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ted Ts'o <tytso@mit.edu>
Cc: Christoph Hellwig <hch@infradead.org>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: [PATCH XFSPROGS 2/3] Build without enabling DEBUG by default
Date: Sat, 30 Jul 2011 12:55:17 -0400	[thread overview]
Message-ID: <20110730165517.GA13918@infradead.org> (raw)
In-Reply-To: <20110726151033.GA18311@infradead.org>

On Tue, Jul 26, 2011 at 11:10:33AM -0400, Christoph Hellwig wrote:
> > This looks much better, and is indeed similar to some other fixes we
> > recently had to put in, probably due to changing make behaviour.
> > 
> > If you add a signoff and a proper description I'll put it into all the
> > repositories.
> 
> Can you at least provide the signoff?  I can take care of the rest if
> this means I can get it in ASAP.

Ted,

can you please give me a signoff for this patch?  I could probably just
put it in anyway given how trivial it is.  But let's just stick to the
proper protocol if we can.


WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Ted Ts'o <tytso@mit.edu>
Cc: Christoph Hellwig <hch@infradead.org>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: [PATCH XFSPROGS 2/3] Build without enabling DEBUG by default
Date: Sat, 30 Jul 2011 12:55:17 -0400	[thread overview]
Message-ID: <20110730165517.GA13918@infradead.org> (raw)
In-Reply-To: <20110726151033.GA18311@infradead.org>

On Tue, Jul 26, 2011 at 11:10:33AM -0400, Christoph Hellwig wrote:
> > This looks much better, and is indeed similar to some other fixes we
> > recently had to put in, probably due to changing make behaviour.
> > 
> > If you add a signoff and a proper description I'll put it into all the
> > repositories.
> 
> Can you at least provide the signoff?  I can take care of the rest if
> this means I can get it in ASAP.

Ted,

can you please give me a signoff for this patch?  I could probably just
put it in anyway given how trivial it is.  But let's just stick to the
proper protocol if we can.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-07-30 16:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 23:50 [PATCH XFSPROGS 1/3] configure.in: Declare a requirement for at least autoconf 2.50 Theodore Ts'o
2011-07-21 23:50 ` Theodore Ts'o
2011-07-21 23:50 ` [PATCH XFSPROGS 2/3] Build without enabling DEBUG by default Theodore Ts'o
2011-07-21 23:50   ` Theodore Ts'o
2011-07-22 14:17   ` Christoph Hellwig
2011-07-22 14:17     ` Christoph Hellwig
2011-07-22 18:30     ` Ted Ts'o
2011-07-22 18:30       ` Ted Ts'o
2011-07-22 18:38       ` Christoph Hellwig
2011-07-22 18:38         ` Christoph Hellwig
2011-07-22 22:30         ` Alex Elder
2011-07-22 22:30           ` Alex Elder
2011-07-22 22:34         ` Ted Ts'o
2011-07-22 22:34           ` Ted Ts'o
2011-07-23  1:32           ` Christoph Hellwig
2011-07-23  1:32             ` Christoph Hellwig
2011-07-26 15:10             ` Christoph Hellwig
2011-07-26 15:10               ` Christoph Hellwig
2011-07-30 16:55               ` Christoph Hellwig [this message]
2011-07-30 16:55                 ` Christoph Hellwig
2011-08-01 21:58                 ` [PATCH] Build using CFLAGS passed in at configure Theodore Ts'o
2011-08-01 21:58                   ` Theodore Ts'o
2011-08-02 10:03                   ` Christoph Hellwig
2011-08-02 10:03                     ` Christoph Hellwig
2011-07-21 23:50 ` [PATCH XFSPROGS 3/3] mkfs: Link against libuuid after liblkid Theodore Ts'o
2011-07-21 23:50   ` Theodore Ts'o
2011-07-22 14:29   ` Christoph Hellwig
2011-07-22 14:29     ` Christoph Hellwig
2011-07-22 14:28 ` [PATCH XFSPROGS 1/3] configure.in: Declare a requirement for at least autoconf 2.50 Christoph Hellwig
2011-07-22 14:28   ` Christoph Hellwig

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=20110730165517.GA13918@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=xfs@oss.sgi.com \
    /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.