[PATCH] x86_64: ignore machine checks from boot time

tree a4a017f686f101b5817f6c1abbc84518335d497e parent cf7bee5a0bf270a4eace0be39329d6ac0136cc47 author Andi Kleen [EMAIL PROTECTED] Sun, 07 Aug 2005 23:42:07 -0700 committer Linus Torvalds [EMAIL PROTECTED] Mon, 08 Aug 2005 00:00:37 -0700 [PATCH] x86_64: ignore machine checks from boot time Don't

[PATCH] ppc32: 8xx: convert fec driver to use work_struct

tree 6bdc59e8f55e86862d71d650e023f6d766ab920c parent 68b47139ea94ab6d05e89c654db8daa99e9a232c author Aristeu Sergio Rozanski Filho [EMAIL PROTECTED] Sun, 07 Aug 2005 23:42:28 -0700 committer Linus Torvalds [EMAIL PROTECTED] Mon, 08 Aug 2005 00:00:38 -0700 [PATCH] ppc32: 8xx: convert fec driver

[PATCH] ppc32: 8xx: fec: fix interrupt handler prototypes

tree 0957806533b81aba75fd2926a9acac9421af13b5 parent fc007ddd609ccfce1cd392e65eed05aba8db32ce author Aristeu Sergio Rozanski Filho [EMAIL PROTECTED] Sun, 07 Aug 2005 23:42:36 -0700 committer Linus Torvalds [EMAIL PROTECTED] Mon, 08 Aug 2005 00:00:39 -0700 [PATCH] ppc32: 8xx: fec: fix interrupt

[PATCH] ppc32: 8xx fix CPM ethernet description

tree 68245a74f6d80f3501084d84d3041e0fab83b72b parent fbccb3d7f56654dbc407f757c884f22d26264e42 author Aristeu Sergio Rozanski Filho [EMAIL PROTECTED] Sun, 07 Aug 2005 23:42:40 -0700 committer Linus Torvalds [EMAIL PROTECTED] Mon, 08 Aug 2005 00:00:39 -0700 [PATCH] ppc32: 8xx fix CPM ethernet

[PATCH] Move the fix to align node_end_pfns to a proper location

tree 80fbfdcae56d07e7bcf27c3927e383ad3e35e378 parent 079da354db3473b56eb938ca53a2cb0804ea9c8c author Ravikiran G Thirumalai [EMAIL PROTECTED] Sun, 07 Aug 2005 23:42:50 -0700 committer Linus Torvalds [EMAIL PROTECTED] Mon, 08 Aug 2005 00:00:39 -0700 [PATCH] Move the fix to align node_end_pfns to

[PATCH] VIA VT8235 PCI quirk

tree 1ab80c4bb980fec383047e8e07a0fb8fa77b5994 parent db6778db7eb1d974e1ae0da326530f09c13585ac author Ivan Kokshaysky [EMAIL PROTECTED] Mon, 08 Aug 2005 12:55:54 +0400 committer Linus Torvalds [EMAIL PROTECTED] Tue, 09 Aug 2005 01:46:24 -0700 [PATCH] VIA VT8235 PCI quirk Like many other

[TG3]: Save initial PCI state before registering the netdevice.

tree 790200fcdef86e91224903394023b964a3a52e47 parent 6fc0b4a7a73a81e74d0004732df358f4f9975be2 author David S. Miller [EMAIL PROTECTED] Sat, 06 Aug 2005 20:35:48 -0700 committer David S. Miller [EMAIL PROTECTED] Sat, 06 Aug 2005 20:35:48 -0700 [TG3]: Save initial PCI state before registering the

Revert [PATCH] PCI: restore BAR values...

tree 893613626de4794a7b13fe6793bdebc79420c433 parent 138b9dd1fd7b44176af4f3b672060c790b0eaf55 author Linus Torvalds [EMAIL PROTECTED] Tue, 09 Aug 2005 08:46:09 -0700 committer Linus Torvalds [EMAIL PROTECTED] Tue, 09 Aug 2005 08:46:09 -0700 Revert [PATCH] PCI: restore BAR values... Revert commit

GIT 0.99.4 preview: current status

Things are looking almost ready for a new release. The list at the end of this message shows what went into the release candidate branch since 0.99.3: Dan's commit walker updates to deal with a packed repository, Johannes fixed quite a lot of problems in the documentation, I did

Re: [PATCH] Teach git push .git/branches shorthand

Hi, On Sun, 7 Aug 2005, Junio C Hamano wrote: I hear a lot of people mention $GIT_DIR/branches/ is confusing. Maybe we should rename it to $GIT_DIR/remote/ directory? I'd prefer $GIT_DIR/remotes/. And I propose another extension: Since the files stored therein right now contain only one

Re: [PATCH] Stash away the original head in ORIG_HEAD when resetting.

Hi, On Sun, 7 Aug 2005, Junio C Hamano wrote: $ git commit -m ORIG_HEAD Since there are not many users of git-commit's *-m* flag right now: Is it necessary to confuse CVS people, who expect to be able to write git commit -m I did this and that I do not want to be too intrusive,

Re: [PATCH] Stash away the original head in ORIG_HEAD when resetting.

Hi, On Mon, 8 Aug 2005, Johannes Schindelin wrote: Hi, On Sun, 7 Aug 2005, Junio C Hamano wrote: $ git commit -m ORIG_HEAD Since there are not many users of git-commit's *-m* flag right now: Is it necessary to confuse CVS people, who expect to be able to write git

[PATCH] Make curl fail on server error

Some http servers return an HTML error page and git reads it as normal data. Adding -f option makes curl fail silently. Signed-off-by: Catalin Marinas [EMAIL PROTECTED] --- git-clone-dumb-http |2 +- git-fetch-script |2 +- git-ls-remote-script |2 +- 3 files changed, 3

Re: [PATCH] Teach git push .git/branches shorthand

Hi, On Mon, 8 Aug 2005, Josef Weidendorfer wrote: IMHO, $GIT_DIR/branches/ is really confusing. Hmmm... in $GIT_DIR/branches/ there are named references to remote (named) references. Not necessarily. The following is perfectly valid: echo rsync://rsync.kernel.org/pub/scm/git/git.git

Re: [PATCH] Teach git push .git/branches shorthand

On Monday 08 August 2005 11:55, Johannes Schindelin wrote: Hi, On Mon, 8 Aug 2005, Josef Weidendorfer wrote: IMHO, $GIT_DIR/branches/ is really confusing. Hmmm... in $GIT_DIR/branches/ there are named references to remote (named) references. Not necessarily. The following is perfectly

Re: use of temporary refs in resolve

Junio C Hamano [EMAIL PROTECTED] wrote: Catalin Marinas [EMAIL PROTECTED] writes: Is FETCH_HEAD going to be preserved by the git-fetch-script operation? It should be, unless, git-pull-script removes it or it is changed to do the fetch as well. I am not quite sure what is being asked

Re: Request for help from binary packaging people.

On Mon, 08 Aug 2005 10:38:44 -0700 Junio C Hamano wrote: For RPM, from my lack of RPM expertise (and RPM capable environment until recently), I have not updated the Prereq: field in git-core.spec.in at all. That Prereq: should be Requires: instead. Prereq: also enforces installation ordering

[PATCH 0/4] Plug some more memory leaks in git

Hello! This set of patches fixes some more memory leaks which I have found in git. Especially the write_sha1_to_fd() leak was noticeable when running git-ssh-push. -- Sergey Vlasov pgpHMTIIDB3N1.pgp Description: PGP signature

[PATCH 1/4] Plug memory leak in read_object_with_reference()

[PATCH] Plug memory leak in read_object_with_reference() When following a reference, read_object_with_reference() did not free the intermediate object data. Signed-off-by: Sergey Vlasov [EMAIL PROTECTED] --- sha1_file.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-)

[PATCH 3/4] Plug memory leak in sha1close()

[PATCH] Plug memory leak in sha1close() sha1create() and sha1fd() malloc the returned struct sha1file; sha1close() should free it. Signed-off-by: Sergey Vlasov [EMAIL PROTECTED] --- csum-file.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) 2207ae4977cbaa84636487ca24bad9d1116f54e0

[PATCH 4/4] Plug memory leak in git-pack-objects

[PATCH] Plug memory leak in git-pack-objects find_deltas() should free its temporary objects before returning. Signed-off-by: Sergey Vlasov [EMAIL PROTECTED] --- pack-objects.c |4 1 files changed, 4 insertions(+), 0 deletions(-) 8b38f80b97affd0d9808b8f276a9e2e04bf03464 diff --git

Re: Request for help from binary packaging people.

* Junio C Hamano ([EMAIL PROTECTED]) wrote: For RPM, from my lack of RPM expertise (and RPM capable environment until recently), I have not updated the Prereq: field in git-core.spec.in at all. I would appreciate somebody to sanity check the list of dependencies. The dependency list Debian

[PATCH 1/1] git_mkstemp() fix

Hi, attached is a bugfix for the newly introduced git_mkstemp() function. /holger git_mkstemp() bugfix --- commit 8cccfa75e0095afd2dd4ec354f2786068c9e7a2f tree 354e00b03039e0c42284442c9764dcd3bf8f608f parent d59a6043a8a7aed97c684fb4f14fe5221df1fcaf author Holger Eitzenberger [EMAIL PROTECTED]

Re: [PATCH] Making CFLAGS compilant with GNU Coding Standards

Pavel Roskin [EMAIL PROTECTED] writes: Quoting GNU Coding Standards (info standards): If there are C compiler options that _must_ be used for proper compilation of certain files, do not include them in `CFLAGS'. Users expect to be able to specify `CFLAGS' freely themselves. Quoting

Re: git revert (Re: pci_update_resource() getting called on sparc64)

Linus Torvalds [EMAIL PROTECTED] writes: On Mon, 8 Aug 2005, Junio C Hamano wrote: Totally untested. I acquired your habit of coding in my e-mail client ;-). Looks good. Although I also have this advanced testing habit of just reading the email and if it looks sane it tested out ok ;)

A simple script to do the reverse of git-push

Hi list, I mentioned in another mail that I needed the opposite of git-push, namely getting all heads, and if they are strict parents of the local refs, just update them. Well, Junio pointed out that it's easy using the available tools, and he was right. The result is attached (and

git-commit-script, was Re: git revert (Re: pci_update_resource() getting called on sparc64)

Hi, On Mon, 8 Aug 2005, Junio C Hamano wrote: * git commit does not take commit message from stdin. I think we should do something like this: [...] And could we rename the *-m* flag at the same time? Because I often catch myself typing git commit -m Some_commit_message Ciao,

Re: Request for help from binary packaging people.

Chris Wright [EMAIL PROTECTED] writes: ... Also, rpm is able to determine the perl dependencies automatically (of course, ditto for shared libraries). I take it to mean that we do not have to explicitly list perl module dependencies. If that is the case then I presume that the current

Re: Request for help from binary packaging people.

* Junio C Hamano ([EMAIL PROTECTED]) wrote: Chris Wright [EMAIL PROTECTED] writes: ... Also, rpm is able to determine the perl dependencies automatically (of course, ditto for shared libraries). I take it to mean that we do not have to explicitly list perl module dependencies. If that

Re: git revert (Re: pci_update_resource() getting called on sparc64)

Linus Torvalds [EMAIL PROTECTED] writes: Or if you want to be more CVS-like, use -F, and accept - for stdin? Yes my vote goes: -m message -c from this commit, literally. -C from this commit, but let me edit the log further. -F from this file. -F - stdin

Re: git-commit-script, was Re: git revert (Re: pci_update_resource() getting called on sparc64)

Linus Torvalds [EMAIL PROTECTED] writes: Most of us don't use 300bps terminals any more, so typing a few extra characters is probably ok. Again you are right. - To unsubscribe from this list: send the line unsubscribe git in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: [PATCH] Making CFLAGS compilant with GNU Coding Standards

On Mon, Aug 08, 2005 at 01:53:24PM -0700, Junio C Hamano wrote: I do want to revisit Makefile issues after 0.99.4, along with the changes Pasky sent several days ago. Please remind me about them after Wednesday. We should discuss (or just do) a reorganization of how we lay out the source

Re: [PATCH] Making CFLAGS compilant with GNU Coding Standards

Hi, On Mon, 8 Aug 2005, Ryan Anderson wrote: [...] We should discuss (or just do) a reorganization of how we lay out the source tree. [...] I, for one, like the layout. There are not yet enough files to merit a hierarchy, and what's more: I can add the source-directory to my PATH and be

Re: git revert (Re: pci_update_resource() getting called on sparc64)

Hi, On Mon, 8 Aug 2005, Junio C Hamano wrote: Linus Torvalds [EMAIL PROTECTED] writes: Or if you want to be more CVS-like, use -F, and accept - for stdin? Yes my vote goes: -m message -c from this commit, literally. -C from this commit, but let me edit the log

git tag can't take piped input?

Apparently I was under a rock sleeping when git-tag-script changed to no longer take input from stdin. So my script which did: TAG=$(echo $TAG_MSG | git-tag-script $RELEASE) echo $TAG .git/refs/tags/$RELEASE Is broken in two ways. First it's no longer building an annotated tag, second it

Re: git revert (Re: pci_update_resource() getting called on sparc64)

[PATCH] Adapt git-cherry and git-rebase-script to latest changes of git commit Teach git-cherry and git-rebase-script to use the -c option, since -m means something different to git-commit-script now. Signed-off-by: Johannes Schindelin [EMAIL PROTECTED] --- git-cherry|2 +-

Make git-rev-tree obsolete

Hi, Junio remarked that Jeff's git-changes-script still uses git-rev-tree, and therefore it should not be removed. This patch changes git-changes-script over to git-rev-list: --- git-changes-script.orig Tue Aug 9 02:21:36 2005 +++ git-changes-script Tue Aug 9 02:20:53 2005 @@ -85,14

Re: [PATCH] Teach git push .git/branches shorthand

Johannes Schindelin [EMAIL PROTECTED] writes: I'd prefer $GIT_DIR/remotes/. And I propose another extension: Since the files stored therein right now contain only one remote string, it should be possible to add the default head(s) to the file. That makes sense. Currently my arrangement is:

Re: use of temporary refs in resolve

Catalin Marinas [EMAIL PROTECTED] writes: OK, I wasn't that clear. Currently git-fetch-script stores the fetched head in the FETCH_HEAD file and git-pull-script uses this file to do the merging (by passing its content to git-resolve-script). Correct. I was not planning to change that

Re: [PATCH] Teach git push .git/branches shorthand

Josef Weidendorfer [EMAIL PROTECTED] writes: My point being that I still can say git pull x some_non_default_head with a file x in .git/branches. Is this currently possible? Not right now, but that is the plan. My understanding of .git/branches was that Cogito uses this as mapping

Re: Make git-rev-tree obsolete

Johannes Schindelin [EMAIL PROTECTED] writes: Junio remarked that Jeff's git-changes-script still uses git-rev-tree, and therefore it should not be removed. This patch changes git-changes-script over to git-rev-list: Just to make things clear, Junio remarked that Cogito also seems to use it

Re: Make git-rev-tree obsolete

On Mon, Aug 08, 2005 at 07:49:26PM -0700, Junio C Hamano wrote: Johannes Schindelin [EMAIL PROTECTED] writes: Junio remarked that Jeff's git-changes-script still uses git-rev-tree, and therefore it should not be removed. This patch changes git-changes-script over to git-rev-list: