On Sun, Feb 10, 2013 at 12:10 AM, Ramkumar Ramachandra
wrote:
> Finn notes in the commit message that it offers no speedup, because
> .gitignore files in every directory still have to be read. I think
> this is silly: we really should be caching .gitignore, and touching it
> only when lstat() rep
Junio C Hamano writes:
> I am not sure about "pushing" part, but the jc/fetch-raw-sha1 topic
> (split from the main jc/hidden-refs topic) should allow your script,
> after the client learns the set of smudged object names, to ask for
>
> git fetch $there $sha1_1 $sha1_2 ...
Well, my out-of-b
Robert Clausecker wrote:
> That is actually a pretty interesting approach. I can use a different
> index file for different deployments. How does this cooperate with bare
> repositories? Aren't they supposed to have no index file at all?
It should work fine in a bare repo.
If you can think of a
That is actually a pretty interesting approach. I can use a different
index file for different deployments. How does this cooperate with bare
repositories? Aren't they supposed to have no index file at all?
Am Samstag, den 09.02.2013, 20:06 -0800 schrieb Jonathan Nieder:
> My advice is to keep a s
Hi Robert,
Robert Clausecker wrote:
> There are two things git archive is missing that are needed in my use
> case:
>
> First, git archive in combination with tar won't remove unneeded files.
> You have to run rm -rf before manually which brings me to the next
> point; git archive can't really ma
There are two things git archive is missing that are needed in my use
case:
First, git archive in combination with tar won't remove unneeded files.
You have to run rm -rf before manually which brings me to the next
point; git archive can't really make incremental updates. Consider an
export that o
Junio C Hamano writes:
> I am not Phil, but if you ask me, I think it is borderline between
> "meh" and "no way we would give a short-and-sweet -i to something
> like this".
I think one reason it was "meh" for me is that we never did an
equivalent of "cvs export" and "svn export", primarily beca
Hi,
Michael J Gruber wrote:
> "reset" can be easily misunderstood as resetting a bisect session to its
> start without finishing it. Clarify that it actually finishes the bisect
> session.
FWIW,
Reviewed-by: Jonathan Nieder
Addressing Andreas's original concern about the discoverability of
'gi
Prevent environment variables and filenames from masquerading
as format strings for printf.
Reported-by: Asheesh Laroia
Signed-off-by: David Aguilar
---
git-difftool--helper.sh | 2 +-
mergetools/p4merge | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/git-difftool--h
Bonjour,
Video youtube : http://youtu.be/Eax9ujtWa60
http://www.lienscash.com/l/w4762
Voici le lien de telechargement de l'application
( appli gratuite à télécharger sur le market )
http://www.lienscash.com/l/w4762
--
To unsubscribe from this list: send the line "unsubscribe git" i
On Sat, Feb 09, 2013 at 03:35:35PM -0800, Junio C Hamano wrote:
> Andreas Mohr writes:
> > The main point of my mail was to stretch the (whether actually intended)
> > *perceived* start <-> stop symmetry
>
> Actually, in that sense, I do no think finish is exactly a good
> wording. The majority
On 2/9/2013 3:06 PM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> Brandon Casey writes:
>>
>>> On Tue, Jan 22, 2013 at 12:38 AM, Jonathan Nieder
>>> wrote:
Brandon Casey wrote:
> Teach append_signoff how to detect a duplicate s-o-b in the commit footer.
> This is in pr
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
As usual, this cycle is expected to last for 8 to 10 weeks, with a
preview -rc0 late next week. I expect that topics that are not
mentioned in
Andreas Mohr writes:
> On Sat, Feb 09, 2013 at 01:53:04PM -0800, Junio C Hamano wrote:
>> Michael J Gruber writes:
>> > After a bisect session, to clean up the bisection state and return to
>> > -the original HEAD, issue the following command:
>> > +the original HEAD (i.e., to finish bisect), i
Hi,
On Sat, Feb 09, 2013 at 01:53:04PM -0800, Junio C Hamano wrote:
> Michael J Gruber writes:
> > After a bisect session, to clean up the bisection state and return to
> > -the original HEAD, issue the following command:
> > +the original HEAD (i.e., to finish bisect), issue the following comma
Jed Brown writes:
> I believe that my use case would be well supported if git could push and
> pull unadvertised refs, as long as basic operations were not slowed down
> by the existence of a very large number of such refs.
I am not sure about "pushing" part, but the jc/fetch-raw-sha1 topic
(spl
Junio C Hamano writes:
> Brandon Casey writes:
>
>> On Tue, Jan 22, 2013 at 12:38 AM, Jonathan Nieder wrote:
>>> Brandon Casey wrote:
>>>
Teach append_signoff how to detect a duplicate s-o-b in the commit footer.
This is in preparation to unify the append_signoff implementations in
>>
Robert Clausecker writes:
> After thinking a while about how to solve the problems I have, I
> consider the following things as a solution to my problem.
>
> Add an option --isolated, -i to git checkout: Check out a branch / tag /
> revision but do not touch the index. This could be used together
Ben Walton writes:
> When passed a local time that was on the boundary of a DST change,
> get_tz_offset returned a GMT offset that was incorrect (off by one
> hour). This is because the time was converted to GMT and then back to
> a time stamp via timelocal() which cannot disambiguate boundary c
Ben Walton writes:
> Neither %s or %z are portable strftime format specifiers.
Well, at least %z is in POSIX; "Some implementations of strftime(3)
lack support for %z format" is fine, tough.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to ma
Michael J Gruber writes:
> "reset" can be easily misunderstood as resetting a bisect session to its
> start without finishing it. Clarify that it actually finishes the bisect
> session.
>
> Reported-by: Andreas Mohr
> Signed-off-by: Michael J Gruber
> ---
> Documentation/git-bisect.txt | 2 +-
This is my (long overdue) re-roll of the series that fixes a
portability issue with git-cvsimport's use of strftime. It also fixes
a but in the original implementation of get_tz (now get_tz_offset).
I ended up taking taking only part of the implementation suggested by
Junio.
The only usage of ge
Neither %s or %z are portable strftime format specifiers. There is no
need for %s in git-cvsimport as the supplied time is already in
seconds since the epoch. For %z, use the function get_tz_offset
provided by Git.pm instead.
Signed-off-by: Ben Walton
---
git-cvsimport.perl |5 -
1 fil
This function has utility outside of the SVN module for any routine
that needs the equivalent of GNU strftime's %z formatting option.
Move it to the top-level Git.pm so that non-SVN modules don't need to
import the SVN module to use it.
The rename makes the purpose of the function clearer.
Signed
When passed a local time that was on the boundary of a DST change,
get_tz_offset returned a GMT offset that was incorrect (off by one
hour). This is because the time was converted to GMT and then back to
a time stamp via timelocal() which cannot disambiguate boundary cases
as noted in its document
Thanks.
--
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
Ramkumar Ramachandra writes:
> Junio C Hamano wrote:
>
>> In other words, does it make sense to read branch.$name.pushremote
>> for all the other irrelevant branches?
>>
>> In yet other words, perhaps adding pushremote_name to the branch
>> structure is unneeded, and you only need this single glo
"reset" can be easily misunderstood as resetting a bisect session to its
start without finishing it. Clarify that it actually finishes the bisect
session.
Reported-by: Andreas Mohr
Signed-off-by: Michael J Gruber
---
Documentation/git-bisect.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletio
Ramkumar Ramachandra writes:
> This is much better than Junio's suggestion to study possible
> implementations on all platforms and designing a generic daemon/
> communication channel. That's no weekend project.
It appears that you misunderstood what I wrote. That was not "here
is a design; I
I think this line should include --local:
https://github.com/git/git/blob/next/contrib/completion/git-completion.bash#L1782
"--global|--system|--file=*)"
This would help for:
git config -l --local
Thanks,
Dasa Paddock--
To unsubscribe from this list: send the line "unsubscribe git" in
th
Duy Nguyen wrote:
> How about this as a start? I did not really check what it does, but it
> does not look complicate enough to pull systemd in.
>
> http://article.gmane.org/gmane.comp.version-control.git/151934
Clever hack. I didn't know that there was a switch called
core.ignoreStat which will
After thinking a while about how to solve the problems I have, I
consider the following things as a solution to my problem.
Add an option --isolated, -i to git checkout: Check out a branch / tag /
revision but do not touch the index. This could be used together with
--work-tree to check out a bran
On Sat, Feb 9, 2013 at 7:53 PM, Ramkumar Ramachandra wrote:
> Ramkumar Ramachandra wrote:
>> What about getting systemd to watch everything for us?
>
> systemd is the perfect candidate!
How about this as a start? I did not really check what it does, but it
does not look complicate enough to pull
On Sat, Feb 09, 2013 at 05:55:26PM +0530, Ramkumar Ramachandra wrote:
> I have two branches: master and gh-pages. master has one submodule
> called foo that gh-pages doesn't. When I try to check out gh-pages
> from master:
>
> warning: unable to rmdir foo: Directory not empty
>
> And the fo
On Thu, Feb 7, 2013 at 9:46 AM, Ted Zlatanov wrote:
> On Thu, 27 Oct 2011 12:05:03 -0400 John Szakmeister
> wrote:
>
> JS> Just wanted to keep folks in the loop. It turns out that the Secrets
> JS> API is still to young. I asked about the format to store credentials
> JS> in (as far as attribu
Hi,
the man page (git version 1.7.10.4) is a bit non-symmetric
since git bisect has the start param, but when searching for "stop"
(nothing more obvious than that, right?),
one comes up empty --> usability issue.
The appropriate action complementary to start appears to be
git bisect reset, thus i
36 matches
Mail list logo