[PATCH] uml: fix the x86_64 build

2005-08-18 Thread Linux Kernel Mailing List
tree bc48f8c3596d8d7e8ca04102c23bd01096669a7e parent 024f474795af7a0d41bd6d60061d78bd66d13f56 author Al Viro [EMAIL PROTECTED] Fri, 19 Aug 2005 01:24:23 -0700 committer Linus Torvalds [EMAIL PROTECTED] Fri, 19 Aug 2005 02:53:58 -0700 [PATCH] uml: fix the x86_64 build asm/elf.h breaks the x86_64

[PATCH] ppc32: fix ppc4xx stb03xxx dma build

2005-08-18 Thread Linux Kernel Mailing List
tree d53e8817bbf738754a63b918517d7d5bea271635 parent 2eaa297ca234eb518673b28dd6f3715d4b292e09 author Matt Porter [EMAIL PROTECTED] Fri, 19 Aug 2005 01:24:25 -0700 committer Linus Torvalds [EMAIL PROTECTED] Fri, 19 Aug 2005 02:53:58 -0700 [PATCH] ppc32: fix ppc4xx stb03xxx dma build Fixes build

[PATCH] ppc32: Fix PPC440SP SRAM controller DCRs

2005-08-18 Thread Linux Kernel Mailing List
tree b61bf02bb31ad01a0fe734dc697dd0c9583e0441 parent 28cd1d17801774561c81a5be53bfb2d632aee2a2 author Matt Porter [EMAIL PROTECTED] Fri, 19 Aug 2005 01:24:26 -0700 committer Linus Torvalds [EMAIL PROTECTED] Fri, 19 Aug 2005 02:53:58 -0700 [PATCH] ppc32: Fix PPC440SP SRAM controller DCRs Fixes the

[PATCH] ide-floppy: fix IDEFLOPPY_TICKS_DELAY

2005-08-18 Thread Linux Kernel Mailing List
tree 58fc485a9ca8d3a89221dd40ee2ae1c110b46598 parent 30d5b64b63fa69af31b2cba32e6d71d68526eec9 author Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] Thu, 18 Aug 2005 22:09:21 +0200 committer Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] Thu, 18 Aug 2005 22:09:21 +0200 [PATCH] ide-floppy: fix

[PATCH] DM9000 - incorrect ioctl() handling

2005-08-18 Thread Linux Kernel Mailing List
tree db587b806019155a84b7e1411f398863c5fdf81f parent 9ef9ac51cc5fa5f5811230b5fb242536b636ff47 author Ben Dooks [EMAIL PROTECTED] Sat, 23 Jul 2005 17:29:38 +0100 committer Jeff Garzik [EMAIL PROTECTED] Fri, 19 Aug 2005 00:59:14 -0400 [PATCH] DM9000 - incorrect ioctl() handling The DM9000 driver

[NET]: Fix comment in loopback driver.

2005-08-18 Thread Linux Kernel Mailing List
tree 19065dd333e9e4dd456f08cb8426544b24ba479e parent 001dd250c1c68667a5c3b74979fa614e2edc9ceb author Ralf Baechle [EMAIL PROTECTED] Fri, 19 Aug 2005 04:05:18 -0700 committer David S. Miller [EMAIL PROTECTED] Fri, 19 Aug 2005 04:05:18 -0700 [NET]: Fix comment in loopback driver. Signed-off-by:

Multi-head pulling series

2005-08-18 Thread Junio C Hamano
Here is the current status of the multi-head download support. [PATCH 1/3] Start adding the $GIT_DIR/remotes/ support. [PATCH 2/3] Multi-head fetch. [PATCH 3/3] Update git-pull to match updated git-fetch. The first one in the series adds support for the long promised

[PATCH 1/3] Start adding the $GIT_DIR/remotes/ support.

2005-08-18 Thread Junio C Hamano
All the necessary parsing code is in git-parse-remote-script; update git-push-script to use it. Signed-off-by: Junio C Hamano [EMAIL PROTECTED] --- Makefile|2 - git-parse-remote-script | 122 +++ git-push-script | 28

[PATCH 3/3] Update git-pull to match updated git-fetch.

2005-08-18 Thread Junio C Hamano
This retires the git-parse-remote script, and allows pull to fetch from multiple remote references. There is no support for resolving more than two heads, so that would be next. Signed-off-by: Junio C Hamano [EMAIL PROTECTED] --- Makefile |2 + git-parse-remote | 79

Re: Git 1.0 Synopis (Draft v4)

2005-08-18 Thread Matthias Urlichs
Hi, Horst von Brand wrote: And teach make(1) about checking out files from git... or just create a co(1) command for git. Ummm... why? make's SCCS support depends on the presence of a SCCS/s.name file for each name. We don't have that. Teaching make about git would be equivalent to teaching

Re: Small team cogito/git setup

2005-08-18 Thread Matthias Urlichs
Hi, Martin Langhoff wrote: Or are we forced to run an 'integration' repo so that we work with a 'star' arrangement? I am actually trying to avoid needing a central repo if possible. Personally, I like the idea of an integration repository. The main reason is that it avoids duplicate work and

Re: [RFC] Patches exchange is bad?

2005-08-18 Thread Catalin Marinas
Johannes Schindelin [EMAIL PROTECTED] wrote: maybe it is time for a quick run through the typical jobs you do with StGIT, much like what Jeff sent the other day? I hope I will find some time this weekend and write some tutorials on an StGIT wiki. -- Catalin - To unsubscribe from this list:

Re: [PATCH] Teach applymbox to keep the Subject: line.

2005-08-18 Thread David Kågedal
Linus Torvalds [EMAIL PROTECTED] writes: On Wed, 17 Aug 2005, Jeff Garzik wrote: 1) Fix applymbox such that it understands RFC822-valid Subject lines which wrap across multiple text lines. It already should do this. 2) Teach it to understand MIME, and not treat the MIME headers like

Re: Multi-head pulling series

2005-08-18 Thread Josef Weidendorfer
On Thursday 18 August 2005 09:24, Junio C Hamano wrote: $ cat $GIT_DIR/remotes/www URL: http://www.kernel.org/pub/scm/git/git.git/ Pull: master:ko-master pu:ko-pu Push: master:master pu:pu foo:bar Isn't this mixing two kinds of information: 1) Some default/persistent

Re: [PATCH/RFC] Allow file removal when git commit --all is used.

2005-08-18 Thread Johannes Schindelin
Hi, On Thu, 18 Aug 2005, Junio C Hamano wrote: After you deleted files from your working tree, automatic git-update-cache used when the --all flag is given to git commit barfs because it lacks the --remove flag. It can be argued that this is a feature; people should be careful and

Re: [RFC] Patches exchange is bad?

2005-08-18 Thread Catalin Marinas
Marco Costalba [EMAIL PROTECTED] wrote: Catalin Marinas wrote: That's how you would normally do development on Linux using StGIT - clone the mainline kernel, create patches in your StGIT tree and submit them either via e-mail or ask the gatekeeper to pull directly from your tree (assuming that

[PATCH] gitweb - Use description instead of content:encoded.

2005-08-18 Thread Yasushi SHOJI
Use description instead of content:encoded. RSS 2.0 Specification doesn't have content:encoded. see http://blogs.law.harvard.edu/tech/rss I've tested this with Mozilla Thunderbird version 1.0.6 (20050802), and seems to be working well. Signed-off-by: Yasushi SHOJI [EMAIL PROTECTED] ---

[PATCH] gitweb - Add author and guid.

2005-08-18 Thread Yasushi SHOJI
Hi all, with this patch and the privious one I just sent, you can run a pretty neat blog site with rss feed for geeks ;) one missing feature is the picture tag Junio asked a while ago ;P yashi Add author and guid. From http://blogs.law.harvard.edu/tech/rss author - Email

[PATCH] Add Makefile target glossary.html

2005-08-18 Thread Johannes Schindelin
This also includes a script which does the sorting, and introduces hyperlinks for every described term. Signed-off-by: Johannes Schindelin [EMAIL PROTECTED] --- Documentation/Makefile |7 +++- Documentation/sort_glossary.pl | 70 2 files

Re: [PATCH] gitweb - Use description instead of content:encoded.

2005-08-18 Thread Sven Verdoolaege
On Thu, Aug 18, 2005 at 11:30:41PM +0900, Yasushi SHOJI wrote: Use description instead of content:encoded. Hmm in snownews this gets displayed as Use instead of .. (http://www.liacs.nl/~sverdool/gitweb.cgi?p=gitweb.git;a=rss) Is that a problem with snownews or with gitweb ? skimo - To

Re: [PATCH] gitweb - Use description instead of content:encoded.

2005-08-18 Thread Kay Sievers
On Thu, Aug 18, 2005 at 11:30:41PM +0900, Yasushi SHOJI wrote: Use description instead of content:encoded. RSS 2.0 Specification doesn't have content:encoded. see http://blogs.law.harvard.edu/tech/rss See here: http://www.notestips.com/80256B3A007F2692/1/NAMO5P9UPQ The description

Re: [PATCH] gitweb - Use description instead of content:encoded.

2005-08-18 Thread Yasushi SHOJI
At Thu, 18 Aug 2005 18:01:09 +0200, Kay Sievers wrote: On Thu, Aug 18, 2005 at 11:30:41PM +0900, Yasushi SHOJI wrote: Use description instead of content:encoded. RSS 2.0 Specification doesn't have content:encoded. see http://blogs.law.harvard.edu/tech/rss See here:

[PATCH] updates for Documentation/howto/using-topic-branches.txt

2005-08-18 Thread Luck, Tony
Small fix (use git branch to make branches, rather than git checkout -b). Optimization for trivial patches (apply to release and merge to test). Three sample scripts appended. Signed-off-by: Tony Luck [EMAIL PROTECTED] --- diff --git a/Documentation/howto/using-topic-branches.txt

Re: [PATCH] gitweb - Use description instead of content:encoded.

2005-08-18 Thread Yasushi SHOJI
At Thu, 18 Aug 2005 17:36:07 +0200, Sven Verdoolaege wrote: On Thu, Aug 18, 2005 at 11:30:41PM +0900, Yasushi SHOJI wrote: Use description instead of content:encoded. Hmm in snownews this gets displayed as Use instead of ..

Re: [PATCH] Teach applymbox to keep the Subject: line.

2005-08-18 Thread Sam Ravnborg
(Also, with proper Signed-off-by: lines it's also always clear that there were other people involved, and that the author of the patch is different from the person who applied it). I almost always handedit my mails and I find myself forgetting to add Signed-off-by from time to time. Is there

Subject: [PATCH] Updates to glossary

2005-08-18 Thread Johannes Schindelin
Changes to the descriptions of tree and tag objects, a link for ent, and descriptions for rewind, rebase and core git were added. Signed-off-by: Johannes Schindelin [EMAIL PROTECTED] --- Documentation/glossary.txt | 28 ++-- 1 files changed, 22 insertions(+), 6

[RFC] Stgit - patch history / add extra parents

2005-08-18 Thread Jan Veldeman
Hi, I like stgit very much, but I feel there is still something missing: stgit is very handy when you use it for patches which should be pushed to mainline rather quickly. But for pacthes which won't be pushed immediately to mainline, it would be usefull to have a history of the patches itself.

Re: [PATCH] Teach applymbox to keep the Subject: line.

2005-08-18 Thread Linus Torvalds
On Thu, 18 Aug 2005, Sam Ravnborg wrote: I almost always handedit my mails and I find myself forgetting to add Signed-off-by from time to time. Is there a simple way to implment a trigger that can check that _I_ signed off the patch before applying it? Well, Junio has been talking about

git-whatchanged -p anomoly?

2005-08-18 Thread Luck, Tony
Yesterday I was all happy ... Linus pulled a couple of changes from my tree, and after I did a pull back from his tree into my linus tracking branch, my status scripts correctly identified the branches that I'd been using to track those changes as being no longer needed. But this morning I ran

Re: Subject: [PATCH] Updates to glossary

2005-08-18 Thread Daniel Barkalow
On Thu, 18 Aug 2005, Johannes Schindelin wrote: tree object:: - An object containing a list of blob and/or tree objects. - (A tree usually corresponds to a directory without - subdirectories). + An object containing a list of file names and modes along with refs + to

Re: Subject: [PATCH] Updates to glossary

2005-08-18 Thread Matthias Urlichs
Hi, Johannes Schindelin wrote: Subject: Subject: [PATCH] Updates to glossary Something is stuttering here -- one Subject: is quite sufficient. -- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED] Disclaimer: The quote was selected randomly. Really. |

Re: Subject: [PATCH] Updates to glossary

2005-08-18 Thread Johannes Schindelin
Hi, On Thu, 18 Aug 2005, Matthias Urlichs wrote: Hi, Johannes Schindelin wrote: Subject: Subject: [PATCH] Updates to glossary Something is stuttering here -- one Subject: is quite sufficient. Subject! Subject! Subject! ;-) My bad. Dscho - To unsubscribe from this list: send the line

Re: Subject: [PATCH] Updates to glossary

2005-08-18 Thread Johannes Schindelin
Hi, On Thu, 18 Aug 2005, Daniel Barkalow wrote: On Thu, 18 Aug 2005, Johannes Schindelin wrote: tree object:: - An object containing a list of blob and/or tree objects. - (A tree usually corresponds to a directory without - subdirectories). + An object containing a list of

Re: symlinked directories in refs are now unreachable

2005-08-18 Thread Matt Draisey
Thanks for committing my one-character patch. In the commit message you said Come to think of it, maybe we should disallow symlink inside .git/refs hierarchy; we update the files there by creat/rename pair, so having symlinks would not work anyway when you do anything that would update

Re: git-whatchanged -p anomoly?

2005-08-18 Thread Linus Torvalds
On Thu, 18 Aug 2005, Luck, Tony wrote: The spurious changes reported by git-whatchanged -p are: Documentation/acpi-hotkey.txt |3 Documentation/kernel-parameters.txt|5 drivers/acpi/osl.c |6 fs/jfs/inode.c

Re: git-whatchanged -p anomoly?

2005-08-18 Thread Junio C Hamano
Luck, Tony [EMAIL PROTECTED] writes: $ git-whatchanged -p test ^linus | diffstat -p1 $ git-diff-tree -p linus test | diffstat -p1 git-whatchanged internally uses git-rev-list which skips merge commits. You need '-m' to cause it not to. $ git-whatchanged -m -p linus..test | diffstat -p1

Re: [PATCH] Teach parse_commit_buffer about grafting.

2005-08-18 Thread Paul Mackerras
Linus Torvalds writes: Paul, I hate to tell you about yet another flag to git-rev-list, but did you realize that in addition to all the other magic flags, there's a flag called --parents? Cool. I didn't realize that. The current version uses it now. Umm. git-rev-list really does

Re: [PATCH] Teach parse_commit_buffer about grafting.

2005-08-18 Thread Johannes Schindelin
Hi, On Fri, 19 Aug 2005, Paul Mackerras wrote: Linus Torvalds writes: Paul, I hate to tell you about yet another flag [...] But why? You're doing such a fine job telling people about flags :-) Umm. git-rev-list really does everything. Rule of thumb: if you _ever_ need to look at any

Re: [PATCH] Teach parse_commit_buffer about grafting.

2005-08-18 Thread Linus Torvalds
On Fri, 19 Aug 2005, Paul Mackerras wrote: Umm. git-rev-list really does everything. Rule of thumb: if you _ever_ need to look at any other internal git information, you're probably doing something wrong, or you've missed yet another flag ;) I still look in [gitdir]/refs/tags/* and

Re: Small team cogito/git setup

2005-08-18 Thread Martin Langhoff
On 8/18/05, Martin Langhoff [EMAIL PROTECTED] wrote: We have a small team of 3, and our main activity is to run local To self: RTFM, specifically, Documentation/tutorial.txt I had read it early on and either didn't get to the end of it, or had forgotten already. Apologies, martin - To

Re: [PATCH/RFC] Allow file removal when git commit --all is used.

2005-08-18 Thread Junio C Hamano
Johannes Schindelin [EMAIL PROTECTED] writes: The patch is for people who thinks the user who uses the --all flag deserves the danger that comes with the convenience. Comments? This is a sane default behaviour. Maybe introduce yet another flag --no-remove, which says that removes should

Re: [PATCH] Teach applymbox to keep the Subject: line.

2005-08-18 Thread Junio C Hamano
Sam Ravnborg [EMAIL PROTECTED] writes: I prefer to add it myself rather than to have it added automatically - but mayve thats you me being a bit mistrusting. The only git- command I use today is git-applymbox. If you did not have that add it myself preference, I would have recommended the

[PATCH] Infamous 'octopus merge'

2005-08-18 Thread Junio C Hamano
This script uses the list of heads and their origin multi-head git fetch left in the $GIT_DIR/FETCH_HEAD file, and makes an octopus merge on top of the current HEAD using them. The implementation tries to be strict for the sake of safety. It insists that your working tree is clean (no local

[Not A Patch] Octopus demo

2005-08-18 Thread Junio C Hamano
Create an empty directory and running this script in there would let you see the original Octopus in action. --- #!/bin/sh test -d .saved-git || { U=http://www.kernel.org/pub/scm/git/git.git GIT_DIR=.saved-git export GIT_DIR git-init-db : $GIT_DIR/FETCH_HEAD h=0

[PATCH] Add commit hook and make the verification customizable.

2005-08-18 Thread Junio C Hamano
There are three hooks: - 'pre-commit' is given an opportunity to inspect what is being committed, before we invoke the EDITOR for the commit message; - 'commit-msg' is invoked on the commit log message after the user prepares it; - 'post-commit' is run after a

Questions on 'cvs migration guide''

2005-08-18 Thread Martin Langhoff
In the section 'Emulating CVS behaviour', where the team setup is described with a team 'merger'. What is not clear is how to deal with project-wide branches. Should they be created in the master repo, and everyone clone a new repo from it? With a team of 10 people, and perhaps 4 or 5 branches,

Cannot use cg-clone over http after packing a public repo

2005-08-18 Thread Martin Langhoff
With todays git and cogito: moodle-git-merge$ git-push-script --all ~/public_html/repos/moodle.git This unpacked the repo completely, in spite if it being local. Anyway, from a remote machine I could do cg-clone and it succeeded, though it took ages: cg-clone

Re: Cannot use cg-clone over http after packing a public repo

2005-08-18 Thread Martin Langhoff
Resolved. I was missing a call to git-update-server-info. It fails to make the objects/info directory, so that had to be done manually. GIT_DIR=~/public_html/repos/moodle.git git-update-server-info error: cannot open /home/martin/public_html/repos/moodle.git/objects/info/packs+ mkdir

[PATCH] Spell __attribute__ correctly in cache.h.

2005-08-18 Thread Jason Riedy
Sun's cc doesn't know __attribute__. Signed-off-by: Jason Riedy [EMAIL PROTECTED] --- cache.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) 4181b19f615b3d56f9fae5f3accd435480aa7d2f diff --git a/cache.h b/cache.h --- a/cache.h +++ b/cache.h @@ -41,7 +41,7 @@ #endif #ifndef

Re: Questions on 'cvs migration guide''

2005-08-18 Thread Linus Torvalds
On Fri, 19 Aug 2005, Martin Langhoff wrote: In the section 'Emulating CVS behaviour', where the team setup is described with a team 'merger'. What is not clear is how to deal with project-wide branches. Should they be created in the master repo, and everyone clone a new repo from it? Just