From: Junio C Hamano <gitster@pobox•com>
To: git@vger•kernel.org
Cc: jnareb@gmail•com, pasky@suse•cz, ltuikov@yahoo•com, paulus@samba•org
Subject: Recent issues
Date: Sat, 07 Jul 2007 00:31:50 -0700 [thread overview]
Message-ID: <7v7ipcbrfd.fsf@assigned-by-dhcp.cox.net> (raw)
Here is a list of recent issues on the list that I am aware of,
but not much have been done on.
To use the Message-ID, you can use:
http://mid.gmane.org/$message_id
where $message_id is the Message-ID without surrounding <>.
* gitweb patches (bunch of them)
From: Matt McCutchen <hashproduct@gmail•com>
Subject: [PATCH] gitweb: snapshot cleanups & support for offering multiple formats
Message-ID: <1183053733.6108.0.camel@mattlaptop2>
From: Matt McCutchen <hashproduct@gmail•com>
Subject: [PATCH] gitweb: make search form generate pathinfo-style URLs
Message-ID: <1183057027.6108.4.camel@mattlaptop2>
From: Matt McCutchen <hashproduct@gmail•com>
Subject: [PATCH] gitweb: make "No commits" in project list gray, not bold green
Message-ID: <1183068922.6108.8.camel@mattlaptop2>
From: Miklos Vajna <vmiklos@frugalware•org>
Subject: [PATCH] gitweb: prefer git_get_project_owner() over get_file_owner()
Message-ID: <20070703221122.GI32766@genesis•frugalware.org>
From: Michael Hendricks <michael@ndrix•org>
Subject: [PATCH] gitweb: configurable width for the projects list Description column
Message-ID: <11835958082458-git-send-email-michael@ndrix•org>
Haven't heard any from gitweb folks about these; I'd take a look
at them if I find time this weekend.
* gitk --left-right
From: Linus Torvalds <torvalds@linux-foundation•org>
Message-ID: <alpine.LFD.0.98.0705051524300.17381@woody•linux-foundation.org>
From: Junio C Hamano <junkio@cox•net>
Message-ID: <7vabwifl23.fsf@assigned-by-dhcp•cox.net>
Paulus?
* gitk tree view fix
From: Brian Downing <bdowning@lavos•net>
Subject: [PATCH] gitk: Fix for tree view ending in nested directories
Message-ID: <20070704212643.GR4087@lavos•net>
Paulus?
* switching branches when b changes between symlink and directory in a/b/c
From: Pierre Habouzit <madcoder@debian•org>
Subject: [BUG (or misfeature?)] git checkout and symlinks
Message-ID: <20070704203541.GA13286@artemis•corp>
Will take a look.
* cherry-pick unexpected conflicts
From: Gerrit Pape <pape@smarden•org>
Subject: Re: unexpected git-cherry-pick conflict
Message-ID: <20070613134336.13661.qmail@c61f4fed932273•315fe32.mid.smarden.org>
* git-apply -R --whitespace=warn
From: Daniel Barkalow <barkalow@iabervon•org>
Message-ID: <Pine.LNX.4.64.0707062155170.6977@iabervon•org>
Subject: Minor bug in git-apply's patch-cleaning
* Use gitattributes for more things.
- Customized "diff -p" markers per path.
From: Linus Torvalds <torvalds@linux-foundation•org>
Subject: Re: [PATCH] Per-path attribute based hunk header selection.
Message-ID: <alpine.LFD.0.98.0707061051020.9434@woody•linux-foundation.org>
Will take a look and try to finish this before 1.5.3-rc1.
next reply other threads:[~2007-07-07 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 7:31 Junio C Hamano [this message]
2007-07-09 9:28 ` Recent issues Paul Mackerras
2007-07-09 10:20 ` Johannes Sixt
[not found] ` <18066.4639.682605.171418@cargo.ozlabs.ibm.com>
2007-07-09 11:03 ` Johannes Sixt
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=7v7ipcbrfd.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jnareb@gmail$(echo .)com \
--cc=ltuikov@yahoo$(echo .)com \
--cc=pasky@suse$(echo .)cz \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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