[PATCH 04/23] object-store: prepare read_object_file to deal with any repo

As read_object_file is a widely used function (which is also regularly used in new code in flight between master..pu), changing its signature is painful is hard, as other series in flight rely on the original signature. It would burden the maintainer if we'd just change the signature. Introduce

[PATCH 05/24] object-store: prepare read_object_file to deal with arbitrary repositories

As read_object_file is a widely used function (which is also regularly used in new code in flight between master..pu), changing its signature is painful is hard, as other series in flight rely on the original signature. It would burden the maintainer if we'd just change the signature. Introduce

[PATCH 04/19] object-store: prepare read_object_file to deal with arbitrary repositories

As read_object_file is a widely used function (which is also regularly used in new code in flight between master..pu), changing its signature is painful is hard, as other series in flight rely on the original signature. It would burden the maintainer if we'd just change the signature. Introduce

Re: [PATCH 04/19] object-store: prepare read_object_file to deal with arbitrary repositories

On Thu, Oct 11, 2018 at 3:01 PM Jonathan Tan wrote: > > > Introduce repo_read_object_file which takes the repository argument, and > > hide the original read_object_file as a macro behind > > NO_THE_REPOSITORY_COMPATIBILITY_MACROS, which we planned for in > > e675765235 (diff.c: remove implicit

Re: [PATCH 04/19] object-store: prepare read_object_file to deal with arbitrary repositories

> Introduce repo_read_object_file which takes the repository argument, and > hide the original read_object_file as a macro behind > NO_THE_REPOSITORY_COMPATIBILITY_MACROS, which we planned for in > e675765235 (diff.c: remove implicit dependency on the_index, 2018-09-21) That commit didn't seem to

[PATCH 04/19] object-store: prepare read_object_file to deal with arbitrary repositories

As read_object_file is a widely used function (which is also regularly used in new code in flight between master..pu), changing its signature is painful is hard, as other series in flight rely on the original signature. It would burden the maintainer if we'd just change the signature. Introduce

Re: is there a canonical doc about how to deal with whitespace issues?

On Mon, 11 Jun 2018, Stefan Beller wrote: > On Fri, Jun 8, 2018 at 10:15 AM Derrick Stolee wrote: > > > > On 6/8/2018 9:18 AM, Robert P. J. Day wrote: > > >for one of my courses, i wanted to write a section about the > > > various techniques for dealing with whitespace issues in git, so > >

Re: is there a canonical doc about how to deal with whitespace issues?

On Fri, Jun 8, 2018 at 10:15 AM Derrick Stolee wrote: > > On 6/8/2018 9:18 AM, Robert P. J. Day wrote: > >for one of my courses, i wanted to write a section about the various > > techniques for dealing with whitespace issues in git, so i started What do you mean by white space issues? That

Re: is there a canonical doc about how to deal with whitespace issues?

On 6/8/2018 9:18 AM, Robert P. J. Day wrote: for one of my courses, i wanted to write a section about the various techniques for dealing with whitespace issues in git, so i started making a list, things like: - running "git diff --check" - "git commit --cleanup=" possibilities -

is there a canonical doc about how to deal with whitespace issues?

for one of my courses, i wanted to write a section about the various techniques for dealing with whitespace issues in git, so i started making a list, things like: - running "git diff --check" - "git commit --cleanup=" possibilities - config options like core.{eol,safecrlf,autocrlf} -

Dear Sir/Million Dollar Deal...

Dear Sir Please this is important and very urgent, I am Mr Ahmed Omar, The Director of the Contractors Award and Review Department with the Nigerian national Petroleum Corporation (NNPC). I need your partnership on an urgent transaction of US$55,000,000.00 (Fiftyfive million United Stated Dollars

Good day I write to you in hope that you will be open minded to consider a business partnership proposal in transaction deal worth millions. All I require from you is honesty and an assurance that you

Guarantee Deal.

I am Capt. Haggard I have special proposal that will do you good, contact me for more understanding. Regard, Capt Haggard nathaniel Email: haggardnathanie...@gmail.com

[PATCH v10 16/20] ref-filter: add an 'rstrip=' option to atoms which deal with refnames

Complimenting the existing 'lstrip=' option, add an 'rstrip=' option which strips `` slash-separated path components from the end of the refname (e.g., `%(refname:rstrip=2)` turns `refs/tags/foo` into `refs`). Signed-off-by: Karthik Nayak ---

[PATCH v9 16/20] ref-filter: add an 'rstrip=' option to atoms which deal with refnames

Complimenting the existing 'lstrip=' option, add an 'rstrip=' option which strips `` slash-separated path components from the end of the refname (e.g., `%(refname:rstrip=2)` turns `refs/tags/foo` into `refs`). Signed-off-by: Karthik Nayak ---

[PATCH v8 15/19] ref-filter: add an 'rstrip=' option to atoms which deal with refnames

Complimenting the existing 'lstrip=' option, add an 'rstrip=' option which strips `` slash-separated path components from the end of the refname (e.g., `%(refname:rstrip=2)` turns `refs/tags/foo` into `refs`). Signed-off-by: Karthik Nayak ---

Re: [PATCH] filter-branch: deal with object name vs. pathname ambiguity in tree-filter

On Mon, Nov 23, 2015 at 01:23:16PM +0100, SZEDER Gábor wrote: > 'git filter-branch' fails complaining about an ambiguous argument, if > a tree-filter renames a path and the new pathname happens to match an > existing object name. > > After the tree-filter has been applied, 'git filter-branch'

[PATCH] filter-branch: deal with object name vs. pathname ambiguity in tree-filter

'git filter-branch' fails complaining about an ambiguous argument, if a tree-filter renames a path and the new pathname happens to match an existing object name. After the tree-filter has been applied, 'git filter-branch' looks for changed paths by running: git diff-index -r --name-only

Business Deal

I have a business deal for you worth 24.5m usd, Reply: wl548...@gmail.com for more details if interested. Thank You --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- To unsubscribe from this list: send the line "unsubscrib

DEAL:

I have a profitable business deal for you, for more info contact me asap Thanks, Tang Lung Peter -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

GET A QUICK CASH LOAN DEAL

VIEW THE ATTACHMENT GET A QUICK LOAN - CASH DEAL LOAN.pdf Description: Adobe PDF document

I have a deal

Please is your email really active? -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: git-send-email doesn't deal with quoted names

On Tue, May 28, 2013 at 01:40:20AM +0200, Jason A. Donenfeld wrote: My commit author name is Jason A. Donenfeld. Because this has a dot, SMTP handling likes to put it in quotes. git-send-email has this line: if (defined $author and $author ne $sender) { With my name, this

git-send-email doesn't deal with quoted names

Hi, My commit author name is Jason A. Donenfeld. Because this has a dot, SMTP handling likes to put it in quotes. git-send-email has this line: if (defined $author and $author ne $sender) { With my name, this always winds up false, because it's comparing 'Jason A. Donenfeld

[PATCH 1/2] Ignore trailing slash in mkdir() on platforms that can't deal with this

/mkdir.c @@ -0,0 +1,24 @@ +#include ../git-compat-util.h +#undef mkdir + +/* for platforms that can't deal with a trailing '/' */ +int compat_mkdir_wo_trailing_slash(const char *dir, mode_t mode) +{ + int retval; + char *tmp_dir = NULL; + size_t len = strlen(dir); + + if (len dir

[PATCH 2/2] Ignore trailing slash in mkdir() on platforms that can't deal with this

Signed-off-by: Joachim Schmitz j...@schmitz-digital.de --- git-compat-util.h | 5 + 1 file changed, 5 insertions(+) diff --git a/git-compat-util.h b/git-compat-util.h index 35b095e..34f040f 100644 --- a/git-compat-util.h +++ b/git-compat-util.h @@ -162,6 +162,11 @@ #define

Re: [PATCH 1/2] Ignore trailing slash in mkdir() on platforms that can't deal with this

As the compat/mkdir.c file includes git-compat-util.h and expects the declaration of the new function to be found in it, it does not make any sense to have this as two patches. I'll squash them into one for now, but it would have been even more complete to have an update to the Makefile to

RE: [PATCH 1/2] Ignore trailing slash in mkdir() on platforms that can't deal with this

From: Junio C Hamano [mailto:gits...@pobox.com] Sent: Friday, August 24, 2012 7:44 PM To: Joachim Schmitz Cc: git@vger.kernel.org Subject: Re: [PATCH 1/2] Ignore trailing slash in mkdir() on platforms that can't deal with this As the compat/mkdir.c file includes git-compat-util.h

[PATCH 8/8] git-remote-mediawiki: properly deal with invalid remote revisions

Some wiki, including https://git.wiki.kernel.org/ have invalid revision numbers (i.e. the actual revision numbers are non-contiguous). Don't die when encountering one. Signed-off-by: Matthieu Moy matthieu@imag.fr --- contrib/mw-to-git/git-remote-mediawiki | 13 + 1 file changed,

[PATCH 8/8] git-remote-mediawiki: properly deal with invalid remote revisions

Some wiki, including https://git.wiki.kernel.org/ have invalid revision numbers (i.e. the actual revision numbers are non-contiguous). Don't die when encountering one. Signed-off-by: Matthieu Moy matthieu@imag.fr --- contrib/mw-to-git/git-remote-mediawiki | 13 + 1 file changed,

sched: rt-group: deal with PI

: Wed Feb 13 15:45:39 2008 +0100 Committer: Ingo Molnar [EMAIL PROTECTED] CommitDate: Wed Feb 13 15:45:39 2008 +0100 sched: rt-group: deal with PI Steven mentioned the fun case where a lock holding task will be throttled. Simple fix: allow groups that have boosted tasks to run

SLUB: Deal with annoying gcc warning on kfree()

: Thu Feb 7 17:47:41 2008 -0800 Committer: Christoph Lameter [EMAIL PROTECTED] CommitDate: Thu Feb 7 17:47:41 2008 -0800 SLUB: Deal with annoying gcc warning on kfree() gcc 4.2 spits out an annoying warning if one casts a const void * pointer to a void * pointer. No warning

xen: deal with pmd being allocated/freed

] AuthorDate: Wed Jan 30 13:33:39 2008 +0100 Committer: Ingo Molnar [EMAIL PROTECTED] CommitDate: Wed Jan 30 13:33:39 2008 +0100 xen: deal with pmd being allocated/freed Deal properly with pmd-level pages being allocated and freed dynamically. We can handle them more or less the same

[POWERPC] 4xx: Deal with 44x virtually tagged icache

] AuthorDate: Wed Oct 31 16:42:19 2007 +1100 Committer: Josh Boyer [EMAIL PROTECTED] CommitDate: Thu Nov 1 07:15:30 2007 -0500 [POWERPC] 4xx: Deal with 44x virtually tagged icache The 44x family has an interesting feature which is a virtually tagged instruction cache (yuck !). So far, we

deal with resource allocation bugs in arcmsr

29 05:08:38 2007 + Committer: Linus Torvalds [EMAIL PROTECTED] CommitDate: Mon Oct 29 07:41:33 2007 -0700 deal with resource allocation bugs in arcmsr a) for type B we should _not_ iounmap() acb-pmu; it's not ioremapped. b) for type B we should iounmap() two regions we _do_

xen: deal with stale cr3 values when unpinning pagetables

] AuthorDate: Tue Oct 16 11:51:30 2007 -0700 Committer: Jeremy Fitzhardinge [EMAIL PROTECTED] CommitDate: Tue Oct 16 11:51:30 2007 -0700 xen: deal with stale cr3 values when unpinning pagetables When a pagetable is no longer in use, it must be unpinned so that its pages can be freed

libata-link: update EH to deal with PMP links

Aug 6 18:36:24 2007 +0900 Committer: Jeff Garzik [EMAIL PROTECTED] CommitDate: Fri Oct 12 14:55:32 2007 -0400 libata-link: update EH to deal with PMP links Update ata_eh_autopsy(), ata_eh_report(), ata_eh_revalidate_and_attach() and ata_eh_recover() to deal with PMP links

deal with alpha section warnings

26 17:34:19 2007 +0100 Committer: Linus Torvalds [EMAIL PROTECTED] CommitDate: Thu Jul 26 11:11:57 2007 -0700 deal with alpha section warnings Signed-off-by: Al Viro [EMAIL PROTECTED] Signed-off-by: Linus Torvalds [EMAIL PROTECTED] --- arch/alpha/kernel/head.S|1

[SPARC32]: Deal with rtc/sun_mostek_rtc conflict.

22 00:37:48 2007 -0700 Committer: David S. Miller [EMAIL PROTECTED] CommitDate: Tue Jul 24 13:24:32 2007 -0700 [SPARC32]: Deal with rtc/sun_mostek_rtc conflict. Signed-off-by: Al Viro [EMAIL PROTECTED] Signed-off-by: David S. Miller [EMAIL PROTECTED] --- arch/sparc/defconfig

[MIPS] lockdep: Deal with interrupt disable hazard in TRACE_IRQFLAGS

: Mon Mar 26 14:48:50 2007 +0100 Committer: Ralf Baechle [EMAIL PROTECTED] CommitDate: Thu Mar 29 23:46:35 2007 +0100 [MIPS] lockdep: Deal with interrupt disable hazard in TRACE_IRQFLAGS Between the mtc0 or di instruction that disables interrupts and the following hazard barrier

[PATCH] knfsd: SUNRPC: teach svc_sendto() to deal with IPv6 addresses

Feb 12 00:53:36 2007 -0800 Committer: Linus Torvalds [EMAIL PROTECTED] CommitDate: Mon Feb 12 09:48:36 2007 -0800 [PATCH] knfsd: SUNRPC: teach svc_sendto() to deal with IPv6 addresses CMSG_DATA comes in different sizes, depending on address family. [EMAIL PROTECTED]: remove