public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: Hans Reiser <reiser@namesys.com>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	reiserfs-dev@namesys.com
Subject: Re: [reiserfs-dev] [PATCH] [BK] ReiserFS cleanups (resend #1)
Date: 03 May 2002 07:53:59 -0400	[thread overview]
Message-ID: <1020426839.1510.124.camel@tiny> (raw)
In-Reply-To: <20020503153750.A877@namesys.com>

On Fri, 2002-05-03 at 07:37, Oleg Drokin wrote:
> Hello!
> 
> On Fri, May 03, 2002 at 07:32:08AM -0400, Chris Mason wrote:
> 
> > It would be could if we could get rid of the cset excludes.  They make
> > the whole thing look a little messy.
> 
> Any hints on how to do that?

Heh, this time I'll try to form actual coherent sentences.  The only way
to get rid of the excludes is to export as a patch and redo the bk
tree.  This is a relatively small set of patches, so I think it's worth
it.

> 
> > ttt is not a good changeset comment ;-)
> And ttt was not changeset commet, but one of the checkins comment, I believe.

Yes, sorry.

> 
> Agreed, I just forgot to change it to something more meaningful at commit time,
> and do not know how to change it later ;)

bk comments should do the trick.

-chris



      reply	other threads:[~2002-05-03 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200205031106.g43B6Mv04822@bitshadow.namesys.com>
2002-05-03 11:32 ` [reiserfs-dev] [PATCH] [BK] ReiserFS cleanups (resend #1) Chris Mason
2002-05-03 11:37   ` Oleg Drokin
2002-05-03 11:53     ` Chris Mason [this message]

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=1020426839.1510.124.camel@tiny \
    --to=mason@suse.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-dev@namesys.com \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox