9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriell@binarydream.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Patch notification emails
Date: Sun,  4 Sep 2005 14:09:00 +0100	[thread overview]
Message-ID: <20050904130900.GL21486@server4.lensbuddy.com> (raw)
In-Reply-To: <ee9e417a05090405595247edc2@mail.gmail.com>

On Sun, Sep 04, 2005 at 08:59:29AM -0400, Russ Cox wrote:
> Even the ones that result from applying a patch
> often are not verbatim copies of what was in the patch.
> I probably edit at least half of the incoming patch code
> after applying it and before pushing it to sources.
I know that, but I don't think there is much I can do about it, maybe
you could edit the patch itself before applying it?

This was one of the main reasons why I gave up on creating a patch
tracking system that keep track of both sources changes and patches, as
I found it impossible to find a sane way to merge both streams of
changes while preserving things like patch(1) comments.

 
> What makes you think that changes to sources are
> being done as none?  
Sorry, I was looking at
http://angband.tip9ug.jp/magic/histgw/n/sources/plan9/sys/src/cmd/tcs/utf.c
(see the [none] and [rsc] at the end of different changes)

Maybe it's a bug in histgw, I still have to ask nashi for the source and
take a look, but I don't think I will have time for that at least until
next week.

"glenda" isn't very useful either, but well, this is just a very
insignificant detail, having comments associated with the changes would
be much more useful IMHO but we have already discussed this and I guess
it just wont happen.

uriel

P.S.: It's just me, or sources is extremely slow?

> 
> % cd /n/sources/plan9/sys/src/9/port
> % ls -lm chan.c
> [rsc] --rw-rw-r-- M 130453 glenda sys 31560 Sep  1 01:19 chan.c
> % 
> 
> Russ


  reply	other threads:[~2005-09-04 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-04 12:14 Uriel
     [not found] ` <ee9e417a05090405316c2f7bab@mail.gmail.com>
2005-09-04 12:39   ` Uriel
2005-09-04 12:59     ` Russ Cox
2005-09-04 13:09       ` Uriel [this message]
2005-09-05  1:15         ` Russ Cox
2005-09-05  1:49 YAMANASHI Takeshi
2005-09-05  2:32 ` Russ Cox

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=20050904130900.GL21486@server4.lensbuddy.com \
    --to=uriell@binarydream.org \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).