pandora smycken rea

Med olika pärlor och smycken åtkomliga från Pandora smycken , pandora berlocker rea i am säker på göra en armband som endast vi kanske har och inget en annars motivet bara för detta är att Pandora gör och sätta upp dessa pärlor och berl

Re: [PATCH] mv: let 'git mv file no-such-dir/' error out

Duy Nguyen writes: > On Tue, Dec 3, 2013 at 3:32 PM, Matthieu Moy wrote: >> Git used to trim the trailing slash, and make the command equivalent to >> 'git mv file no-such-dir', which created the file no-such-dir (while the >> trailing slash explicitly stated that it could only be a directory).

Re: Business

Dear friend, Good day! This is an investment proposal for you on behalf of Capt. Addanki Gopinath (RTD). He wants you to be his foreign partner, investments and funds manager to invest his funds USD68million into Real Estate or any other lucrative business in your country. If you are interest

Re: gitk refresh keeps showing dangling commits

On Fri, Nov 29, 2013 at 4:27 PM, Thibault Kruse wrote: > and in gitk, I select "Reload"(Ctrl-F5), and I still see both commits, > not just commit foo. Do you use the menu entry Reload, or the keyboard shortcut Ctrl+F5? The shortcut was changed a while ago to Shift+F5. http://git.661346.n2.nabble

Re: Command-line git Vs IDE+plugin?

On Tue, Nov 19, 2013 at 6:20 PM, Matthieu Moy wrote: > One thing the command-line does well is to give names to concepts > (basically, command names, option names, ...). It's easy to write in a > tutorial or an email "run the command 'git foo'". It's less easy to > write "click on that red button,

Re: [PATCH jk/remove-deprecated] stop installing git-tar-tree link

Jonathan Nieder venit, vidit, dixit 03.12.2013 00:37: > When the built-in "git tar-tree" command (a thin wrapper around "git > archive") was removed in 925ceccf (tar-tree: remove deprecated > command, 2013-11-10), the build continued to install a non-functioning > git-tar-tree command in gitexecdir

Use mongoose to test smart-http unconditionally?

I was thinking of an alternative to apache for testing smart-http so that most of http tests could always run. Mongoose [1] looks like a good candidate to bundle with git. Just one pair of source files, mongoose.[ch], a mainloop wrapper and we have an http server. Just wondering, do we rely on any

Re: Command-line git Vs IDE+plugin?

On 19/11/13 06:11, Matthieu Moy wrote: > I was wondering whether others had similar (or not) experience. In > particular, as a teacher, I'm wondering whether I should push my > students towards the GUI in the IDE, or advise them to keep using the > command-line (we teach them git with the command-l

Re: slow git-cherry-pick.

On Wednesday 04 of December 2013 08:07:23 Duy Nguyen wrote: > On Wed, Dec 4, 2013 at 3:13 AM, Thomas Rast wrote: > > Paweł Sikora writes: > > > > Umm, there's a gem here that the thread missed so far: > >> my git repo isn't very big[1] but it's checked out on the linear lvm > >> where random i/o

Re: [PATCH 2/3] gitweb: Add a feature for adding more branch refs

On Tue, 2013-12-03 at 21:38 +0100, Jakub Narębski wrote: > On Tue, Dec 3, 2013 at 9:15 PM, Junio C Hamano wrote: > > Krzesimir Nowak writes: > > > >> @@ -626,6 +640,17 @@ sub feature_avatar { > >> return @val ? @val : @_; > >> } > >> > >> +sub feature_extra_branch_refs { > >> + my (@br

Re: [RFC 02/11] remote.c: add infrastructure for parsing --prune options

On Wed, Dec 4, 2013 at 12:44 PM, Michael Haggerty wrote: > +void argv_push_prune_option(struct argv_array *argv, > + struct prune_option *prune_option) > +{ > + if (prune_option->prune != -1) > + argv_array_pushf(argv, > +

Re: [PATCH 1/3] gitweb: Move check-ref-format code into separate function

On Tue, 2013-12-03 at 20:38 +0100, Jakub Narębski wrote: > On Tue, Dec 3, 2013 at 8:02 PM, Junio C Hamano wrote: > > Krzesimir Nowak writes: > > >> +sub check_ref_format { > >> + my $input = shift || return undef; > >> + > >> + # restrictions on ref name according to git-check-ref-format

Re: [PATCH] mv: let 'git mv file no-such-dir/' error out

On Wed, Dec 4, 2013 at 3:44 PM, Matthieu Moy wrote: > Duy Nguyen writes: > >> On Tue, Dec 3, 2013 at 3:32 PM, Matthieu Moy wrote: >> There's something we probably should check. In d78b0f3 ([PATCH] >> git-mv: add more path normalization - 2006-08-16), it mentions about >> >> git mv something/ som

[PATCH 1/5] gitweb: Add a comment explaining the meaning of $/

So future reader will know what does it mean without running "perldoc perlvar". Signed-off-by: Krzesimir Nowak --- gitweb/gitweb.perl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl index 68c77f6..ee61f9e 100755 --- a/gitweb/gitweb.perl +++ b/gitweb/

[PATCH 0/5] Show extra branch refs in gitweb v6

First patch just adds a comment I though would be useful when trying to understand how config parsing is done. Second patch splits some code to a function. Third patch fixes validation functions to return either 0 or 1, instead of undef or passed $input. Fourth patch adds the extra-branch-featur

[PATCH 2/5] gitweb: Move check-ref-format code into separate function

This check will be used in more than one place later. Signed-off-by: Krzesimir Nowak Reviewed-by: Junio C Hamano Reviewed-by: Jakub Narębski --- gitweb/gitweb.perl | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl ind

[PATCH 4/5] gitweb: Add a feature for adding more branch refs

Allow extra-branch-refs feature to tell gitweb to show refs from additional hierarchies in addition to branches in the list-of-branches view. Signed-off-by: Krzesimir Nowak Reviewed-by: Junio C Hamano Reviewed-by: Jakub Narębski --- Documentation/gitweb.conf.txt | 37 +++ gitwe

[PATCH 3/5] gitweb: Return plain booleans in validation methods

Users of validate_* passing "0" might get failures on correct name because of coercion of "0" to false in code like: die_error(500, "invalid ref") unless (check_ref_format ("0")); Signed-off-by: Krzesimir Nowak --- gitweb/gitweb.perl | 45 + 1 file cha

[PATCH 5/5] gitweb: Denote non-heads, non-remotes branches

Given two branches residing in refs/heads/master and refs/wip/feature the list-of-branches view will present them in following way: master feature (wip) When getting a snapshot of a 'feature' branch, the tarball is going to have name like 'project-wip-feature-.tgz'. Signed-off-by: Krzesimir Nowak

Re: [PATCH 0/3] Show extra branch refs in gitweb

On Tue, 2013-12-03 at 15:56 +0100, Krzesimir Nowak wrote: > First patch just splits some code to a function, second patch adds the > extra-branch-refs feature and third one adds some visual > differentation of branches from non-standard ref directories. > > Krzesimir Nowak (3): > gitweb: Move ch

Re: [PATCH 1/5] gitweb: Add a comment explaining the meaning of $/

On Wed, Dec 4, 2013 at 2:42 PM, Krzesimir Nowak wrote: > So future reader will know what does it mean without running "perldoc > perlvar". Hmmm... shouldn't future reader know it anyway? It is not that cryptic. I'd say it is idiomatic Perl. Besides, it is not the only place where we set input

Re: [PATCH 1/5] gitweb: Add a comment explaining the meaning of $/

On Wed, 2013-12-04 at 16:11 +0100, Jakub Narębski wrote: > On Wed, Dec 4, 2013 at 2:42 PM, Krzesimir Nowak > wrote: > > > So future reader will know what does it mean without running "perldoc > > perlvar". > > Hmmm... shouldn't future reader know it anyway? It is not that cryptic. > I'd say it

Re: [PATCH 2/5] gitweb: Move check-ref-format code into separate function

On Wed, Dec 4, 2013 at 2:43 PM, Krzesimir Nowak wrote: > This check will be used in more than one place later. > > Signed-off-by: Krzesimir Nowak > Reviewed-by: Junio C Hamano > Reviewed-by: Jakub Narębski All right, that is nice refactoring. > --- > gitweb/gitweb.perl | 17 +---

Re: [PATCH 3/5] gitweb: Return plain booleans in validation methods

On Wed, Dec 4, 2013 at 2:43 PM, Krzesimir Nowak wrote: > Users of validate_* passing "0" might get failures on correct name > because of coercion of "0" to false in code like: > die_error(500, "invalid ref") unless (check_ref_format ("0")); I would say that the problem was that validate_sth() su

problems with git --git-dir on windows 7

Hello, We are using git on windows7(git-version 1.8.1; see below) and we get the following problem in using the command 'git --git-dir=' C:\UserTemp\git\appli3>git  --git-dir=C:\UserTemp\git\appli3 tag fatal: Not a git repository: 'C:\UserTemp\git\appli3' but the repository is well defined,as

Re: [PATCH 1/5] gitweb: Add a comment explaining the meaning of $/

On Wed, Dec 4, 2013 at 10:46 AM, Krzesimir Nowak wrote: > On Wed, 2013-12-04 at 16:11 +0100, Jakub Narębski wrote: >> On Wed, Dec 4, 2013 at 2:42 PM, Krzesimir Nowak >> wrote: >> >> > So future reader will know what does it mean without running "perldoc >> > perlvar". >> >> Hmmm... shouldn't fut

Re: [RFC 02/11] remote.c: add infrastructure for parsing --prune options

On 12/04/2013 01:57 PM, Duy Nguyen wrote: > On Wed, Dec 4, 2013 at 12:44 PM, Michael Haggerty > wrote: >> +void argv_push_prune_option(struct argv_array *argv, >> + struct prune_option *prune_option) >> +{ >> + if (prune_option->prune != -1) >> + argv

Re: [PATCH 1/5] gitweb: Add a comment explaining the meaning of $/

On Wed, Dec 4, 2013 at 4:46 PM, Krzesimir Nowak wrote: > On Wed, 2013-12-04 at 16:11 +0100, Jakub Narębski wrote: >> On Wed, Dec 4, 2013 at 2:42 PM, Krzesimir Nowak >> wrote: >> >> > So future reader will know what does it mean without running "perldoc >> > perlvar". >> >> Hmmm... shouldn't futu

[PATCH v2] mv: let 'git mv file no-such-dir/' error out

Git used to trim the trailing slash, and make the command equivalent to 'git mv file no-such-dir', which created the file no-such-dir (while the trailing slash explicitly stated that it could only be a directory). This patch skips the trailing slash removal for the destination path. The path with

Re: [PATCH 1/5] gitweb: Add a comment explaining the meaning of $/

On Wed, Dec 4, 2013 at 6:34 PM, Jakub Narębski wrote: > On Wed, Dec 4, 2013 at 4:46 PM, Krzesimir Nowak > wrote: >> On Wed, 2013-12-04 at 16:11 +0100, Jakub Narębski wrote: >>> On Wed, Dec 4, 2013 at 2:42 PM, Krzesimir Nowak >>> wrote: >>> >>> > So future reader will know what does it mean wit

Re: [PATCH] mv: let 'git mv file no-such-dir/' error out

Duy Nguyen writes: > On Wed, Dec 4, 2013 at 3:44 PM, Matthieu Moy > wrote: >> Duy Nguyen writes: >> >>> On Tue, Dec 3, 2013 at 3:32 PM, Matthieu Moy wrote: >>> There's something we probably should check. In d78b0f3 ([PATCH] >>> git-mv: add more path normalization - 2006-08-16), it mentions abo

Re: [PATCH] mv: let 'git mv file no-such-dir/' error out

Junio C Hamano writes: > It seems that t7001 needs some face-lifting, by the way. Perhaps > after this patch solidifies. Yes. I followed the style of surrounding code, but it could be reformatted to follow the current standard. I have no time for it now. -- Matthieu Moy http://www-verimag.ima

Re: [PATCH 2/3] gitweb: Add a feature for adding more branch refs

Krzesimir Nowak writes: > On Tue, 2013-12-03 at 21:38 +0100, Jakub Narębski wrote: >> On Tue, Dec 3, 2013 at 9:15 PM, Junio C Hamano wrote: >> > Krzesimir Nowak writes: >> > >> >> @@ -626,6 +640,17 @@ sub feature_avatar { >> >> return @val ? @val : @_; >> >> } >> >> >> >> +sub feature_ex

Re: [PATCH 4/5] gitweb: Add a feature for adding more branch refs

On Wed, Dec 4, 2013 at 2:43 PM, Krzesimir Nowak wrote: > > Allow extra-branch-refs feature to tell gitweb to show refs from > additional hierarchies in addition to branches in the list-of-branches > view. > > Signed-off-by: Krzesimir Nowak > Reviewed-by: Junio C Hamano > Reviewed-by: Jakub Naręb

Re: [PATCH 3/5] gitweb: Return plain booleans in validation methods

Jakub Narębski writes: > On Wed, Dec 4, 2013 at 2:43 PM, Krzesimir Nowak > wrote: > >> Users of validate_* passing "0" might get failures on correct name >> because of coercion of "0" to false in code like: >> die_error(500, "invalid ref") unless (check_ref_format ("0")); > > I would say that t

Re: Use mongoose to test smart-http unconditionally?

On Wed, Dec 4, 2013 at 2:53 AM, Duy Nguyen wrote: > I was thinking of an alternative to apache for testing smart-http so > that most of http tests could always run. Mongoose [1] looks like a > good candidate to bundle with git. Just one pair of source files, > mongoose.[ch], a mainloop wrapper and

Re: Use mongoose to test smart-http unconditionally?

On Wed, Dec 04, 2013 at 10:13:11AM -0800, Shawn Pearce wrote: > On Wed, Dec 4, 2013 at 2:53 AM, Duy Nguyen wrote: > > I was thinking of an alternative to apache for testing smart-http so > > that most of http tests could always run. Mongoose [1] looks like a > > good candidate to bundle with git.

Re: [PATCH 5/5] gitweb: Denote non-heads, non-remotes branches

On Wed, Dec 4, 2013 at 2:43 PM, Krzesimir Nowak wrote: > Given two branches residing in refs/heads/master and refs/wip/feature > the list-of-branches view will present them in following way: > > master > feature (wip) > > When getting a snapshot of a 'feature' branch, the tarball is going to > ha

Build issue for git 1.8.5.1 under Mac OS X 10.8 (Mountain Lion)

Hi all, Over the years I have built many versions of git and released them on hmug.org. git 1.8.5.1 builds just fine under OS 10.7 (Lion) and 10.9 (Mavericks), but the build fails (also for 1.8.5) on 10.8 (Mountain Lion): GIT_VERSION = 1.8.5.1 * new build flags CC credential-store.o In

Re: [PATCH 1/1] tests: fix gzip with exported GZIP variable in environment

On Tue, Dec 03, 2013 at 10:21:35AM -0800, Junio C Hamano wrote: > Jeff King writes: > > > There are a few options I see: > > > > 1. Drop $GZIP variable, and hard-code the prerequisite check to > > "gzip", which is what is being tested. > > > > 2. Keep $GZIP (but rename it to $GIT_GZIP),

Re: Fwd: [PATCH 4/5] Replace {pre,suf}fixcmp() with {starts,ends}_with()

On Tue, Dec 03, 2013 at 09:24:40PM +0100, Christian Couder wrote: > > I skimmed the patch and didn't notice any problems. It's > > whitespace-damaged by gmail, of course. The simplest thing is probably > > to just point us at a public repo with the commit, if you have one. > > Ok, the commit is i

Re: How to resume broke clone ?

On Thu, Nov 28, 2013 at 11:15:27AM -0800, Shawn Pearce wrote: > >> - better integration with git bundles, provide a way to seamlessly > >> create/fetch/resume the bundles with "git clone" and "git fetch" > > We have been thinking about formalizing the /clone.bundle hack used by > repo on Android

Re: Use mongoose to test smart-http unconditionally?

Duy Nguyen writes: > I was thinking of an alternative to apache for testing smart-http > so that most of http tests could always run. Mongoose [1] looks > like a good candidate to bundle with git. Just one pair of source > files, mongoose.[ch], a mainloop wrapper and we have an http > server. H

Re: [PATCH v2] difftool: Change prompt to display the number of files in the diff queue

Eric Sunshine writes: >> + setenv ("GIT_DIFF_PATH_COUNTER", counterstr.buf, 1); >> + setenv ("GIT_DIFF_PATH_TOTAL", totalstr.buf, 1); >> + >> retval = run_command_v_opt(spawn_arg, RUN_USING_SHELL); > > Would run_command_v_opt_cd_env() be more appropriate than setenv() + > run_

Re: [RFC 00/11] Make reference pruning more configurable

Michael Haggerty writes: > But even though "--prune=" is no longer needed to prevent tag > nuking, it might be useful to somebody for other purposes, and > therefore I am submitting it to the list as an RFC. Maybe there is a > use case associated with non-branch, non-tag references, like perhaps

Re: [PATCH 1/5] gitweb: Add a comment explaining the meaning of $/

Martin Langhoff writes: > On Wed, Dec 4, 2013 at 10:46 AM, Krzesimir Nowak > wrote: >> On Wed, 2013-12-04 at 16:11 +0100, Jakub Narębski wrote: >>> On Wed, Dec 4, 2013 at 2:42 PM, Krzesimir Nowak >>> wrote: >>> >>> > So future reader will know what does it mean without running "perldoc >>> >

Re: [PATCH 2/5] gitweb: Move check-ref-format code into separate function

Krzesimir Nowak writes: > This check will be used in more than one place later. > > Signed-off-by: Krzesimir Nowak > Reviewed-by: Junio C Hamano Again, I do not think I reviewed this exact version. Nor did I say that use of the "... or return undef" is a good idea. > Reviewed-by: Jakub Narębs

Re: [PATCH 0/5] Show extra branch refs in gitweb v6

Krzesimir Nowak writes: > First patch just adds a comment I though would be useful when trying > to understand how config parsing is done. > > Second patch splits some code to a function. > > Third patch fixes validation functions to return either 0 or 1, > instead of undef or passed $input. > >

Re: Fwd: [PATCH 4/5] Replace {pre,suf}fixcmp() with {starts,ends}_with()

Christian Couder writes: > Ok, the commit is in the use_starts_ends_with branch on this github repo: > > https://github.com/chriscool/git.git I looked at the patches, and they looked alright. The endgame needs to be on a separate topic to be held until a distant future, though. Will queue. Th

Re: Fwd: [PATCH 4/5] Replace {pre,suf}fixcmp() with {starts,ends}_with()

Junio C Hamano writes: > Christian Couder writes: > >> Ok, the commit is in the use_starts_ends_with branch on this github repo: >> >> https://github.com/chriscool/git.git > > I looked at the patches, and they looked alright. The endgame needs > to be on a separate topic to be held until a dist

Re: [PATCH 1/1] tests: fix gzip with exported GZIP variable in environment

Jeff King writes: > On Tue, Dec 03, 2013 at 10:21:35AM -0800, Junio C Hamano wrote: > >> Jeff King writes: >> >> > There are a few options I see: >> > >> > 1. Drop $GZIP variable, and hard-code the prerequisite check to >> > "gzip", which is what is being tested. >> > ... >> > I think I'

[RFC/WIP PATCH 0/4] less ignorance of submodules for ignore=all

This is my current work in progress. Sergey it would be awesome if you could test these and tell me whether the behaviour is what you would expect. Once that is settled I will add some tests and possibly clean up some code. Since nobody spoke against this change of behavior I assume that we agree

[RFC/WIP PATCH 1/4] disable complete ignorance of submodules for index <-> HEAD diff

If the value of ignore for submodules is set to "all" we would not show whats actually committed during status or diff. This can result in the user committing unexpected submodule references. Lets be nicer and always show whats in the index. Signed-off-by: Heiko Voigt --- builtin/diff.c

[RFC/WIP PATCH 2/4] fix 'git add' to skip submodules configured as ignored

If submodules are configured as ignore=all they are not shown by status. Lets also ignore them when adding files to the index. This avoids that users accidentially add ignored submodules with: git add . We achieve this by reading the submodule config and thus correctly initializing the infrastruct

[RFC/WIP PATCH 3/4] teach add -f option for ignored submodules

When the user wants to bypass the ignored status configured by submodule..ignore=all it is now allowed by using the -f option. Signed-off-by: Heiko Voigt --- builtin/add.c | 49 + submodule.c | 10 ++ submodule.h | 1 + 3 files changed

[RFC/WIP PATCH 4/4] always show committed submodules in summary after commit

If an ignored submodule is committed because is was registered in the index we should always show that to the user in the printed summary after commit. Signed-off-by: Heiko Voigt --- builtin/commit.c | 1 + 1 file changed, 1 insertion(+) diff --git a/builtin/commit.c b/builtin/commit.c index 6a

Re: Use mongoose to test smart-http unconditionally?

On Wed, Dec 04, 2013 at 12:09:09PM -0800, Junio C Hamano wrote: > Duy Nguyen writes: > > > I was thinking of an alternative to apache for testing smart-http > > so that most of http tests could always run. Mongoose [1] looks > > like a good candidate to bundle with git. Just one pair of source

Re: [RFC/WIP PATCH 0/4] less ignorance of submodules for ignore=all

On Wed, Dec 04, 2013 at 11:16:59PM +0100, Heiko Voigt wrote: > * The git diff $commit question Junio mentioned here[1] it does not yet >show diffs of ignore=all submodules. Forgot to add this here: [1] http://article.gmane.org/gmane.comp.version-control.git/238348 -- To unsubscribe from this

Re: [RFC/WIP PATCH 0/4] less ignorance of submodules for ignore=all

Heiko Voigt writes: > This is my current work in progress. Sergey it would be awesome if you > could test these and tell me whether the behaviour is what you would > expect. Once that is settled I will add some tests and possibly clean up > some code. > > Since nobody spoke against this change of

Re: git filter-branch --directory-filter oddity

On Tue, Dec 3, 2013 at 5:44 PM, Martin Langhoff wrote: > Am I doing it wrong? Looks like I was doing something wrong. Apologies about the noise. cheers, m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs

Re: Use mongoose to test smart-http unconditionally?

Jeff King writes: > The rollout would be: > > 1. add contrib/mongoose/* > > 2. add test-httpd which links against mongoose, built by default in the > Makefile > > 3. convert lib-httpd/apache.conf into mongoose config as necessary > > 4. convert lib-httpd.sh to run test-httpd instead

Publishing "filtered branch repositories" - workflow / recommendations?

Hi folks. currently working on a project based on Moodle (the LMS that got me into git in the first place). This is a highly modular software, and I would like to maintain a bunch of "out of tree" modules in a single repository, and be able to publish them in "per-module" repositories. So I would

Re: Re: [RFC/WIP PATCH 0/4] less ignorance of submodules for ignore=all

On Wed, Dec 04, 2013 at 02:32:46PM -0800, Junio C Hamano wrote: > Heiko Voigt writes: > > > This is my current work in progress. Sergey it would be awesome if you > > could test these and tell me whether the behaviour is what you would > > expect. Once that is settled I will add some tests and po

Re: Use mongoose to test smart-http unconditionally?

Jeff King wrote: > I don't know if it is worth all that much effort, though. I suppose it > could get us more exposure to the httpd tests, but I do not know if it > would be a good idea to turn them on by default anyway. They touch > global machine resources (like ports) that can cause conflicts o

Re: [PATCH] contrib/git-credential-gnome-keyring.c: small stylistic cleanups

Thanks, will queue. -- 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: Use mongoose to test smart-http unconditionally?

On Thu, Dec 5, 2013 at 6:28 AM, Jonathan Nieder wrote: > Jeff King wrote: > >> I don't know if it is worth all that much effort, though. I suppose it >> could get us more exposure to the httpd tests, but I do not know if it >> would be a good idea to turn them on by default anyway. They touch >> g

What's cooking in git.git (Dec 2013, #01; Wed, 4)

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. There are quite a many topics that have been left over from the previous round. I haven't rewound the tip of 'next' yet, but I am planning to d

[PATCH v2 0/3] Teaching "git push" to map pushed refs

The 'master' refspec in "git fetch origin master" used to mean "We grab their 'master' branch, but we do not store it in any of our remote-tracking branches." but in modern Git, the remote-tracking branch that would receive updates from 'master' with a corresponding "git fetch origin" (without any

[PATCH v2 3/3] push: also use "upstream" mapping when pushing a single ref

When the user is using the 'upstream' mode, these commands: $ git push $ git push origin would find the 'upstream' branch for the current branch, and then push the current branch to update it. However, pushing a single branch explicitly, i.e. $ git push origin $(git symbolic-ref --s

[PATCH v2 1/3] builtin/push.c: use strbuf instead of manual allocation

The command line arguments given to "git push" are massaged into a list of refspecs in set_refspecs() function. This was implemented using xmalloc, strcpy and friends, but it is much easier to read if done using strbuf. Signed-off-by: Junio C Hamano --- builtin/push.c | 35 ++

[PATCH v2 2/3] push: use remote.$name.push as a refmap

Since f2690487 (fetch: opportunistically update tracking refs, 2013-05-11), we stopped taking a non-storing refspec given on the command line of "git fetch" literally, and instead started mapping it via remote.$name.fetch refspecs. This allows $ git fetch origin master from the 'origin' repo

Thin pack

Hi, What are the difference between pre 1.8.5 and 1.8.5 about thin pack support? Could you describe thin pack? >From the doc, it says --thin is default option. Is that true? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More

Re: What's cooking in git.git (Dec 2013, #01; Wed, 4)

On Thu, Dec 5, 2013 at 8:23 AM, Junio C Hamano wrote: > * aa/transport-non-positive-depth-only (2013-11-26) 1 commit > (merged to 'next' on 2013-11-27 at b01f05b) > + transport: catch non positive --depth option value > > Will merge to 'master'. Don't. It breaks smart-http [1]. I'm starting t

Re: Use mongoose to test smart-http unconditionally?

On Wed, Dec 04, 2013 at 02:53:13PM -0800, Junio C Hamano wrote: > If it involves making things not tested with apache, I'd actually be > less supportive for the whole plan. I hadn't really considered that angle. Apache is a much more realistic real-world deployment. We give advice for it in git-h

[PATCH] Additional git-archive tests

Interplay between paths specified in three ways now tested: * After a : in the tree-ish, * As a pathspec in the command, * By virtue of the current working directory Note that these tests are based on the behaviours as found in 1.8.5. They may not be intentional. They were developed to regression

Re: Use mongoose to test smart-http unconditionally?

On Wed, Dec 04, 2013 at 03:28:00PM -0800, Jonathan Nieder wrote: > For what it's worth, when I build git and run tests I tend to be in an > environment with apache available, but I'm too lazy to configure git's > tests to pick the right port and make sure it is reserved and so on. > Perhaps there'

[PATCH] clone,fetch: catch non positive --depth option value

Instead of simply ignoring the value passed to --depth option when it is zero or negative, catch and report it as an error to let people know that they were using the option incorrectly. Original-patch-by: Andrés G. Aragoneses Signed-off-by: Nguyễn Thái Ngọc Duy --- This replaces aa/transport-n

[PATCH] t5551: test fetch.c:backfill_tags() code

This makes sure the second fetch with transport helper code path is exercised in the test suite. Signed-off-by: Nguyễn Thái Ngọc Duy --- This should catch the problem by aa/transport-non-positive-depth-only. The GIT_TEST_BACKFILL_TAGS is bad but I don't know any sure way to verify it, assuming

Re: Thin pack

On Thu, Dec 5, 2013 at 8:44 AM, 乙酸鋰 wrote: > What are the difference between pre 1.8.5 and 1.8.5 about thin pack support? No idea. > Could you describe thin pack? It gets a bit technical. Under the hood objects are deltified, only the differences between an object and its base are stored. If bo

Re: How to resume broke clone ?

On Wed, Dec 4, 2013 at 12:08 PM, Jeff King wrote: > On Thu, Nov 28, 2013 at 11:15:27AM -0800, Shawn Pearce wrote: > >> >> - better integration with git bundles, provide a way to seamlessly >> >> create/fetch/resume the bundles with "git clone" and "git fetch" >> >> We have been thinking about for

Re: Build issue for git 1.8.5.1 under Mac OS X 10.8 (Mountain Lion)

On 12/04/2013 07:48 PM, Marius Schamschula wrote: Hi all, Over the years I have built many versions of git and released them on hmug.org. git 1.8.5.1 builds just fine under OS 10.7 (Lion) and 10.9 (Mavericks), but the build fails (also for 1.8.5) on 10.8 (Mountain Lion): GIT_VERSION = 1.8.5.

Re: Fwd: [PATCH 4/5] Replace {pre,suf}fixcmp() with {starts,ends}_with()

On Wed, Dec 4, 2013 at 11:02 PM, Junio C Hamano wrote: > Junio C Hamano writes: > >> Christian Couder writes: >> >>> Ok, the commit is in the use_starts_ends_with branch on this github repo: >>> >>> https://github.com/chriscool/git.git >> >> I looked at the patches, and they looked alright. The

Re: What's cooking in git.git (Dec 2013, #01; Wed, 4)

On Thu, Dec 5, 2013 at 2:23 AM, Junio C Hamano wrote: > > * cc/starts-n-ends-with (2013-12-04) 4 commits > - replace {pre,suf}fixcmp() with {starts,ends}_with() > - strbuf: introduce starts_with() and ends_with() > - builtin/remote: remove postfixcmp() and use suffixcmp() instead > - environme