public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-kernel@vger.kernel.org
Cc: bitkeeper-users@bitmover.com
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Mon, 15 Dec 2003 15:11:26 +0300	[thread overview]
Message-ID: <20031215151126.3fe6e97a.vsu@altlinux.ru> (raw)
In-Reply-To: 2259130000.1071469863@[10.10.2.4]

On Sun, 14 Dec 2003 22:31:04 -0800 Martin J. Bligh wrote:

> One thing that I've wished for in the past which looks like it *might*
> be trivial to do is to grab a raw version of the patch you already
> put out in HTML format, eg if I surf down changesets and get to a page
> like this:
> 
> http://linus.bkbits.net:8080/linux-2.5/patch@1.1522?nav=index.html|ChangeSet@-2w|cset@1.1522
> 
> except it got html formatted, so I can't play with it easily. Is there
> any way to provide the raw format of that? If not, or you don't want to,
> no problem - would just be convenient. This isn't a open source vs not
> issue, it's just I often want one fix without the whole tree, and it'd
> be a convenient place to grab it.

You almost can do this now - in most cases, copying the text from
Mozilla gives a good patch. The only problem is that the HTML
generation code seems to have a bug - it correctly escapes '<' as
"&lt;" and '>' as "&gt;", but does not escape '&' as "&amp;", and this
occasionally leads to problems.

I see another missing feature - there does not seem to be a way to
order the changesets by the order of merging them into the tree. E.g.
when you look at the linux-2.4 changesets, you will now find XFS all
over the place - even before 2.4.23, while it really has been merged
after 2.4.23.


  reply	other threads:[~2003-12-15 12:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14 17:21 RFC - tarball/patch server in BitKeeper Larry McVoy
2003-12-14 23:05 ` Keith Owens
2003-12-14 23:44   ` Larry McVoy
2003-12-15  0:25     ` Keith Owens
2003-12-15  3:47       ` Larry McVoy
2003-12-14 23:17 ` Tupshin Harper
2003-12-14 23:43   ` Larry McVoy
2003-12-15  0:19     ` Tupshin Harper
2003-12-15  3:46       ` Larry McVoy
2003-12-15  6:07         ` Tupshin Harper
2003-12-15 16:02           ` Larry McVoy
2003-12-15 19:52             ` Tupshin Harper
2003-12-15  6:31 ` Martin J. Bligh
2003-12-15 12:11   ` Sergey Vlasov [this message]
2003-12-15 13:27     ` Ben Collins
2003-12-15 16:24       ` Sergey Vlasov
2003-12-15 16:32         ` Larry McVoy
2003-12-15 18:31         ` Andrea Arcangeli
2003-12-15 18:58           ` Larry McVoy
2003-12-15 19:40             ` Andrea Arcangeli
2003-12-15 21:44               ` Larry McVoy
2003-12-15 22:02                 ` Andrea Arcangeli
2003-12-15 22:14                   ` Larry McVoy
2003-12-15 22:44                     ` Tupshin Harper
2003-12-15 23:13                       ` Andrea Arcangeli
2003-12-15 22:36                 ` Tupshin Harper
2003-12-15 22:46                   ` Larry McVoy
2003-12-15 23:08                     ` Tupshin Harper
2003-12-17  4:47                       ` Matthew D. Pitts
2003-12-15 15:42   ` Larry McVoy
2003-12-15 15:55     ` Martin J. Bligh
2003-12-15 23:18 ` Chris Frey
2003-12-21 20:02 ` Pavel Machek
2003-12-21 20:46   ` John Bradford
2003-12-24  1:49   ` Larry McVoy

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=20031215151126.3fe6e97a.vsu@altlinux.ru \
    --to=vsu@altlinux.ru \
    --cc=bitkeeper-users@bitmover.com \
    --cc=linux-kernel@vger.kernel.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