On 24/04/2019 19.16, Junio C Hamano wrote:
> Piotr Krukowiecki writes:
>
>> I was familiar with "git checkout revision -- file".
>>
>> But it updates both working tree and index. I had some changes in
>> index (staged) and "git checkout HEAD -- file" silently overwritten
>> it. Well, probably
On 19/03/2019 17.46, Dimitri Joukoff wrote:
> Thanks for the feedback.
>
> Whilst I understand the options that you've both proposed, the intent
> was to enable the Swift Package Manager to mirror repositories in a
> transparent way. I'll look into whether these options can be
> implemented in
On 07/23/2018 06:10 PM, demerphq wrote:
> On Sun, 22 Jul 2018 at 01:59, brian m. carlson
> wrote:
>> I will admit that I don't love making this decision by myself, because
>> right now, whatever I pick, somebody is going to be unhappy. I want to
>> state, unambiguously, that I'm trying to make
On 07/19/2018 06:52 PM, Sitaram Chamarty wrote:
> On Thu, Jul 19, 2018 at 03:24:54PM +0300, Basin Ilya wrote:
>> Hi.
>>
>> I have two github accounts, one is for my organization and I want git to
>> automatically choose the correct ssh `IdentityFile` based on
On Thu, Jul 19, 2018 at 03:24:54PM +0300, Basin Ilya wrote:
> Hi.
>
> I have two github accounts, one is for my organization and I want git to
> automatically choose the correct ssh `IdentityFile` based on the clone URL:
>
> g...@github.com:other/publicrepo.git
>~/.ssh/id_rsa
> g
On Mon, May 28, 2018 at 09:27:18AM -0400, Robert P. J. Day wrote:
[snipped the rest because I really don't know]
> more to the point, is that actually what the "update" hook does? i
> just looked at the shipped sample, "update.sample", and it seems to be
> related to tags:
>
> #!/bin/sh
>
On Wed, May 16, 2018 at 04:02:53PM -0400, Konstantin Ryabitsev wrote:
> On 05/16/18 15:37, Jeff King wrote:
> > Yes, that's pretty close to what we do at GitHub. Before doing any
> > repacking in the mother repo, we actually do the equivalent of:
> >
> > git fetch --prune ../$id.git +refs/*:refs
Ken,
On Mon, Dec 05, 2016 at 11:04:44PM +0100, Fredrik Gustafsson wrote:
> On Mon, Dec 05, 2016 at 03:33:51PM -0500, ken edward wrote:
> > I am currently using svn with apache+mod_dav_svn to have a single
> > repository with multiple projects. Each of the projects is controlled
> > by an access co
On 08/12/2016 08:07 PM, Jon Forrest wrote:
>
>
> On 8/12/16 6:11 AM, Sitaram Chamarty wrote:
>
>> At present gitolite is -- AFAIK -- the only "pure server side", "no GUI"
>> solution for access control, and has some interesting features that more
&g
On 07/24/2016 09:37 AM, Jon Forrest wrote:
> This an announcement of Pro Git Reedited 2nd Edition, which is
> a substantial edit of Chacon and Straub's Pro Git 2nd Edition.
> I spent a lot of time tightening it up and maybe clearing
> up some explanations.
>
> The pdf is downloadable at:
> https:/
On 11/11/15 15:42, Jeremy Morton wrote:
> On 11/11/2015 09:51, Sitaram Chamarty wrote:
>> I can only repeat what I said before: it's not all black and white.
>>
>> Reducing the opportunity to make mistakes is useful for everyone, even
>> expetrs. Especially stuff t
On 11/11/15 14:58, Jeremy Morton wrote:
> On 11/11/2015 04:48, Sitaram Chamarty wrote:
>> A lot of things in Unix do follow that "give you rope to hang yourself"
>> philosophy. I used to (and to *some* extent still do) think like that,
>> but some years of suppo
On 11/11/15 01:34, Jeremy Morton wrote:
> On 10/11/2015 18:12, Stefan Beller wrote:
>> On Tue, Nov 10, 2015 at 8:31 AM, Jeremy Morton wrote:
>>> It's recently come to my attention that the "git alias" config functionality
>>> ignores all aliases that would override existing Git commands. This see
On 08/22/2015 04:25 AM, Guido Vranken wrote:
> List,
>
> I would like to report security vulnerabilities in git. Due to the
> sensitive nature of security-impacting bugs I would like to know if
> there's a dedicated e-mail address for this, so that the issues at
> play can be patched prior to a co
On 07/03/2015 11:06 PM, Junio C Hamano wrote:
> Sitaram Chamarty writes:
>
>> On 06/25/2015 05:41 AM, Junio C Hamano wrote:
>>> Sitaram Chamarty writes:
>>>
>>>> This *is* documented, but I'm curious why this distinction is made.
>>>
>
On 06/25/2015 05:41 AM, Junio C Hamano wrote:
> Sitaram Chamarty writes:
>
>> This *is* documented, but I'm curious why this distinction is made.
>
> I think it is from mere laziness, and also in a smaller degree
> coming from an expectation that --stdin would be fe
Hi all,
"git name-rev" does not accept abbreviated SHAs if --stdin is used,
though it works when the SHA is given directly on the command line:
$ git version
git version 2.4.3
$ git name-rev --tags d73f544
d73f544 tags/v3.6.3~29
$ git name-rev --tags --stdin <<< d73f544
d7
On 06/09/2015 07:55 PM, Jeff King wrote:
> On Tue, Jun 09, 2015 at 07:36:20PM +0530, Sitaram Chamarty wrote:
>
>>> This patch prints the latest SHA-1 before the forced push in full. He
>>> then can do
>>>
>>> git push +:
>>>
>>> H
On 06/09/2015 05:42 PM, Duy Nguyen wrote:
> From a thread on Hacker News. It seems that if a user does not have
> access to the remote's reflog and accidentally forces a push to a ref,
> how does he recover it? In order to force push again to revert it
> back, he would need to know the remote's old
On 06/08/2015 09:44 PM, Konstantin Khomoutov wrote:
> On Mon, 8 Jun 2015 9:45:17 -0500
> wrote:
>
> [...]
>> My question is, will GIT work with MS access forms, queries, tables,
>> modules, etc?
> [...]
>
> Git works with files. So in principle it will work with *files*
> containing your MS acc
On 05/18/2015 04:28 PM, John McIntyre wrote:
> 2015-05-18 11:26 GMT+01:00 Heiko Voigt :
>> If you want a simple tool using ssh-keys have a look at gitolite[1].
>> It quite simple to setup and with it you can specify all kinds of access
>> rights.
>
> That's adding a separate level of complexity.
On 05/11/2015 03:49 AM, Junio C Hamano wrote:
> The current thinking is to model this after the "repo" tool.
> Prepare a reasonably up-to-date bundle file on the server side,
For people using gitolite, the server side issues of generating a
reasonably up-to-date bundle *and* enabling it for resu
On 04/12/2015 04:55 PM, Yi, EungJun wrote:
> On Wed, Apr 8, 2015 at 8:08 PM, Tony Finch wrote:
>> Yi, EungJun wrote:
>>>
>>> I want a way to response a remote message when a client send any kind
>>> of request. Is it possible?
>>
>> Yes, though you need a wrapper around git. Recent versions of gi
On 03/04/2015 08:55 PM, Michael J Gruber wrote:
> Yes, that article has a few really weak lines of arguments, such as the
> tutorial count.
Here's his definition of the main draw of a DVCS:
No, the only thing that a DVCS gets you, by definition, is that
everyone gets a copy of the full o
On 12/30/2014 11:18 PM, Junio C Hamano wrote:
> Sitaram Chamarty writes:
>
>> Just wanted to say there's a little script at [1] that saves the certificate
>> blobs generated on the server side by "git push --signed".
>>
>> Quoting from the source:
>
Hello,
Just wanted to say there's a little script at [1] that saves the certificate
blobs generated on the server side by "git push --signed".
Quoting from the source:
# Collects the cert blob on push and saves it, then, if a certain number of
# signed pushes have been seen, processes all the "s
Hi git core devs,
Any chance I could persuade you to set the GIT_PUSH_CERT* environment
variables for the update (and post-update) hooks also?
Background: gitolite "takes over" the update hook [1] for authorisation
and enforcement, and I want to avoid taking over the pre-receive hook
also in orde
On 11/27/2014 06:50 AM, Jonathan Nieder wrote:
> Hi Hugh,
>
> Hugh Davenport wrote:
>
>> Where is the best place to report a security vulnerability in git?
>
> Current practice is to contact Junio C Hamano .
> Cc-ing Jeff King isn't a bad idea while at it.
>
> We should probably set up a maili
Hi all,
I've just created a general purpose TOTP "gatekeeper" that is designed
to gate access to any service on any server/OS (as long as traffic can
only go *through* the TOTP gatekeeper).
The inspiration was Konstantin Ryabitsev's implementation of two-factor
authentication for kernel.org -- fr
uld fit, or are you on windows?
Ouch. That hurt.
> On 25 July 2014 05:11, Sitaram Chamarty wrote:
>> On 07/25/2014 03:45 AM, Sheldon Els wrote:
>>> Hi
>>>
>>> A small tool I wrote that is useful for some workflows. I thought it'd
>>> be worth shar
On 07/25/2014 03:45 AM, Sheldon Els wrote:
> Hi
>
> A small tool I wrote that is useful for some workflows. I thought it'd
> be worth sharing. https://github.com/sheldon/git-feature-branch/
As far as I can tell it's just a shell script; does it really need
installation instructions, and if so can
On 05/11/2014 11:34 PM, Junio C Hamano wrote:
Sitaram Chamarty writes:
But what I was looking for was validation from git.git folks of the idea
of replicating what "git clone -l" does, for an *existing* repo.
For example, I'm assuming that bringing in only the objects -- wit
On 05/11/2014 08:41 AM, Storm-Olsen, Marius wrote:
On 5/10/2014 9:10 PM, Sitaram Chamarty wrote:
1. Clone remote repo
2. Hack hack hack
3. Fork repo on server
4. Push changes to your own remote repo
is equally efficient.
Your suggestions are good for a manual setup where
On 05/11/2014 07:04 AM, Storm-Olsen, Marius wrote:
On 5/10/2014 8:04 PM, Sitaram Chamarty wrote:
On 05/11/2014 02:32 AM, Junio C Hamano wrote: That's an interesting
thread and it's recent too. However, it's about clone (though the
intro email mentions other commands also).
I
On 05/11/2014 02:32 AM, Junio C Hamano wrote:
Sitaram Chamarty writes:
Is there a trick to optimising a push by telling the receiver to pick up
missing objects from some other repo on its own server, to cut down even
more on network traffic?
So, hypothetically,
git push user@host:repo1
Hi,
Is there a trick to optimising a push by telling the receiver to pick up
missing objects from some other repo on its own server, to cut down even
more on network traffic?
So, hypothetically,
git push user@host:repo1 --look-for-objects-in=repo2
I'm aware of the alternates mechanism, but
On 05/05/2014 09:48 AM, Chris Packham wrote:
Hi,
I know there are a few people on this list that do git training in
various forms. At $dayjob I've been asked to run a few training
sessions in house. The initial audience is SW developers so they are
fairly clued up on VCS concepts and most have s
On 04/28/2014 02:22 PM, Jeremy Morton wrote:
On 28/04/2014 03:30, Sitaram Chamarty wrote:
On 04/28/2014 01:03 AM, Johan Herland wrote:
Yeah, sure. Author and Date (and Committer, for that matter) is just
metadata, and the current branch name is simply just another kind of
metadata. All of them
On 04/28/2014 11:37 AM, David Kastrup wrote:
Johan Herland writes:
Obviously, the feature would necessarily have to be optional, simply
because Git would have to keep understanding the old commit object
format for a LONG time (probably indefinitely), and there's nothing
you can do to prevent o
On 04/28/2014 01:03 AM, Johan Herland wrote:
On Sun, Apr 27, 2014 at 7:38 PM, Jeremy Morton wrote:
On 27/04/2014 10:09, Johan Herland wrote:
On Sun, Apr 27, 2014 at 1:56 AM, Jeremy Morton
wrote:
Currently, git records a checksum, author, commit date/time, and commit
message with every commit
On 03/09/2014 10:57 PM, Julian Brost wrote:
On 07.03.2014 22:04, Jeff King wrote:
Yes, this is a well-known issue. The only safe operation on a
repository for which somebody else controls hooks and config is to
fetch from it (upload-pack on the remote repository does not
respect any dangerous co
On 01/28/2014 05:58 PM, Kacper Kornet wrote:
> On Mon, Jan 27, 2014 at 10:58:29AM -0800, Jonathan Nieder wrote:
>> Hi,
>
>> Kacper Kornet wrote:
>
>>> The change in release numbering also breaks down gitolite v2 setups. One
>>> of the gitolite commands, gl-compile-conf, expects the output of git
On 11/16/2013 01:30 PM, Jiang Xin wrote:
> 2013/11/15 Sitaram Chamarty :
>> On 11/15/2013 07:55 PM, Sitaram Chamarty wrote:
[snip]
>> I should add that the Gitolite model is: the user doesn't need to know
>> about namespaces, because namespaces are just things that the
On 11/15/2013 07:55 PM, Sitaram Chamarty wrote:
> On 11/15/2013 01:49 PM, Jiang Xin wrote:
>> GIT_NAMESPACE is designed to be used mainly on the server side, that
>> the server can serve multiple git repositories while share one single
>> repository storage using different G
On 11/15/2013 01:49 PM, Jiang Xin wrote:
> GIT_NAMESPACE is designed to be used mainly on the server side, that
> the server can serve multiple git repositories while share one single
> repository storage using different GIT_NAMESPACE settings.
>
> Since we know that one remote repository hosts mu
I can't resist...
On 11/14/2013 08:12 PM, Stephen Bash wrote:
[snipped some stuff from Peff]
[snipped 60 lines of python]
In honor of your last name, here's what I would do if I needed to log
ref updates (and wasn't using Gitolite):
#!/bin/bash
# -- use this as a post-receive hook
while read
On 11/14/2013 01:44 PM, Jeff King wrote:
> On Thu, Nov 14, 2013 at 05:48:50AM +0530, Sitaram Chamarty wrote:
>
>> Is there *any* way we can preserve a reflog for a deleted branch,
>> perhaps under logs/refs/deleted//full/ref/name ?
>
> I had patches to do something lik
2013, at 11:09, Jeff King wrote:
>
>> On Thu, Nov 14, 2013 at 04:26:46PM +0530, Sitaram Chamarty wrote:
>>
>>>> I do not know about any particular debate in git circles, but I assume
>>>> Sitaram is referring to this incident:
>>>>
>>>> http
On 11/14/2013 04:39 PM, Jeff King wrote:
> On Thu, Nov 14, 2013 at 04:26:46PM +0530, Sitaram Chamarty wrote:
>
>>> I do not know about any particular debate in git circles, but I assume
>>> Sitaram is referring to this incident:
>>>
>>> https://groups.
On 11/14/2013 01:37 PM, Jeff King wrote:
> On Thu, Nov 14, 2013 at 08:56:07AM +0100, Thomas Rast wrote:
>
>>> Whatever it was that happened to a hundred or more repos on the Jenkins
>>> project seems to be stirring up this debate in some circles.
>>
>> Making us so curious ... and then you just le
e.
sitaram
On 06/01/2013 11:26 PM, Ramkumar Ramachandra wrote:
> Sitaram Chamarty wrote:
>> I think I'd have to be playing with *several* branches simultaneously
>> before I got to the point of forgetting the branch name!
>
> Yeah, I work on lots of small unrelated things:
- describe when it is still applicable
- tell people where to go for most normal cases
Signed-off-by: Sitaram Chamarty
---
ref: http://thread.gmane.org/gmane.comp.version-control.git/159633. Yes
it's very old but better late than never.
Documentation/howto/setup-git-server-over-htt
On 09/20/2013 04:48 AM, shirish शिरीष wrote:
> Hi all,
> First of all a big thank you to all for making git. With it being fast
> and cheap (in relation to bandwidth and sizes for subsequent checkouts
> as well as CPU usage) . Please CC me if somebody does answer this mail
> as I'm not subscribed t
On 09/18/2013 03:42 PM, Nicolas Adenis-Lamarre wrote:
> Thanks a lot for your answer.
> That's really good arguments that i was waiting for and that i have
> not get until now.
>
> My comprehension now :
> - it's not easy to maintain several versions of a binary file in parallel.
> So basically, i
On 09/18/2013 01:15 AM, Nicolas Adenis-Lamarre wrote:
> Ooops. It seems that each time somebody says these two words together,
> people hate him, and he is scorned by friends and family.
>
> However,
> - gitolite implement it (but gitolite is not git).
No. It pretends to implement it, for people
On 09/10/2013 02:18 AM, Niels Basjes wrote:
> As we all know the hooks ( in .git/hooks ) are not cloned along with
> the code of a project.
> Now this is a correct approach for the scripts that do stuff like
> emailing the people responsible for releases or submitting the commit
> to a CI system.
On 08/14/2013 12:40 PM, Andres Perera wrote:
> On Wed, Aug 14, 2013 at 2:02 AM, Sitaram Chamarty wrote:
>> On 08/14/2013 07:14 AM, Junio C Hamano wrote:
>>> Sitaram Chamarty writes:
>>>
>>>> # all reflog entries that are not on a branch, tag, or remote
On 08/14/2013 07:14 AM, Junio C Hamano wrote:
> Sitaram Chamarty writes:
>
>> # all reflog entries that are not on a branch, tag, or remote
>> d1 = !gitk --date-order $(git log -g --pretty=%H) --not --branches
>> --tags --remotes
>> # all dangling co
On 08/13/2013 10:19 PM, Junio C Hamano wrote:
> Duy Nguyen writes:
>
>> On Mon, Aug 12, 2013 at 3:37 PM, David Jeske wrote:
>>> Is there currently any way to say "hey, git, show me what commits are
>>> dangling that might be lost in the reflog?"
>>
>> How do you define dangling commits? When you
On Sat, Jun 1, 2013 at 11:26 PM, Ramkumar Ramachandra
wrote:
> Sitaram Chamarty wrote:
>> I think I'd have to be playing with *several* branches simultaneously
>> before I got to the point of forgetting the branch name!
>
> Yeah, I work on lots of small unrelated things:
On Sat, Jun 1, 2013 at 3:17 PM, Ramkumar Ramachandra wrote:
> Jeff King wrote:
>> Why don't the branch names have significance? If I deleted branch "foo"
>> yesterday evening, wouldn't I want to be able to say "show me foo from
>> 2pm yesterday" or even "show me all logs for foo, so that I can pic
Hi,
Is there a way to prevent reflog deletion when the branch is deleted?
The last entry could simply be a line where the second SHA is all 0's.
--
Sitaram
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info a
On Wed, Mar 27, 2013 at 8:33 PM, Junio C Hamano wrote:
> Sitaram Chamarty writes:
>
>> On Wed, Mar 27, 2013 at 9:17 AM, Junio C Hamano wrote:
>>
>>> To be paranoid, you may want to set transfer.fsckObjects to true,
>>> perhaps in your ~/.gitconfig.
>>
On Wed, Mar 27, 2013 at 9:17 AM, Junio C Hamano wrote:
> To be paranoid, you may want to set transfer.fsckObjects to true,
> perhaps in your ~/.gitconfig.
do we have any numbers on the overhead of this?
Even a "guesstimate" will do...
--
To unsubscribe from this list: send the line "unsubscribe
On Wed, Feb 27, 2013 at 2:01 AM, Jens Lehmann wrote:
> Am 26.02.2013 17:07, schrieb Junio C Hamano:
>> "jones.noamle" writes:
>>
>>> # git gc
>>> Counting objects: 44626, done.
>>> Delta compression using up to 8 threads.
>>> Compressing objects: 100% (7756/7756), done.
>>> fatal: sha1 file '.git
On Mon, Feb 11, 2013 at 4:24 AM, Junio C Hamano wrote:
> Jeff King writes:
>
>> On Sun, Feb 10, 2013 at 01:25:38PM -0800, Jonathan Nieder wrote:
>>
>>> Ethan Reesor wrote:
>>>
>>> > I have a git user set up on my server. It's prompt is set to
>>> > git-prompt and it's git-shell-commands is empty.
On Wed, Feb 6, 2013 at 9:27 PM, R. Diez wrote:
> Hi there:
>
> I asked a few days ago whether I could easily diff 2 file revisions with the
> mouse in gitk, but I got no reply yet, see here:
>
>
>How to diff two file revisions with the mouse (with gitk)
>https://groups.google.com/forum/#!
On Mon, Feb 4, 2013 at 10:22 PM, Junio C Hamano wrote:
> Tomas Carnecky writes:
>
>> That's what `git checkout` is for. And I would even argue that it's the
>> better
>> choice in your situation because it would delete files from /var/www/foo
>> which
>> you have deleted in your repo. git archi
On 02/03/2013 11:41 PM, Robert Clausecker wrote:
>
> Am Sonntag, den 03.02.2013, 21:55 +0530 schrieb Sitaram Chamarty:
>> Could you help me understand why piping it to tar (actually 'tar -C
>> /dest/dir -x') is not sufficient to achieve what you want?
>
> Pip
On 02/03/2013 07:48 PM, Robert Clausecker wrote:
> Hello!
>
> git currently has the archive command that allows to save an arbitrary
> revision into a tar or zip file. Sometimes it is useful to not save this
> revision into an archive but to directly put all files into an arbitrary
> directory. Cu
On 01/31/2013 12:23 PM, Scott Yan wrote:
> Sitaram:
>
> It seems I must host my central repo on Gitolite first...
There is no "must" but yes it is a decent solution and can, in
principle, do the kind of checking you want if you set it up to do that.
Please note that I don't use that mode and, a
On 01/31/2013 11:38 AM, Tomas Carnecky wrote:
> On Thu, 31 Jan 2013 13:52:32 +0800, Scott Yan wrote:
>> Hello everyone:
>>
>> The user info of git client (user name and email) is set by the users
>> themselves, so , how to avoid userA pretend to be userB?
>>
>> Git server could authentication the
others too.
> > On 30.01.2013, at 16:59, Sitaram Chamarty wrote:
> >
> >> I'm curious... what's wrong with 'git checkout html' from the git repo
> >> and just browsing them using a web browser?
> >
> > Hm, do you mean "make html",
On Wed, Jan 30, 2013 at 7:28 PM, Max Horn wrote:
>
> On 30.01.2013, at 12:54, John Keeping wrote:
>
>> On Wed, Jan 30, 2013 at 12:46:47PM +0100, Max Horn wrote:
>>> does anybody know a website where one can view that latest git
>>> documentation? Here, "latest" means "latest release" (though being
On Sat, Jan 12, 2013 at 6:43 PM, Jeff King wrote:
> On Sat, Jan 12, 2013 at 06:39:52AM +0530, Sitaram Chamarty wrote:
>
>> > 1. The repo has a ref R pointing at commit X.
>> >
>> > 2. A user starts a push to another ref, Q, of commit Y that builds on
>>
Thanks for the very detailed answer.
On Fri, Jan 11, 2013 at 10:12 PM, Jeff King wrote:
> On Fri, Jan 11, 2013 at 04:40:38PM +0530, Sitaram Chamarty wrote:
>
>> I find a lot of info on how to recover from and/or repair a repo that
>> has missing (or corrupted) objects.
>>
On Sat, Dec 22, 2012 at 11:57 PM, Junio C Hamano wrote:
> Andreas Schwab writes:
>
>> This is not limited to HEAD, any ref may want to be set up as a symref
>> at a remote repo. For example, I want to set up a symref master ->
>> trunk at a repository I have no shell access to.
>
> That is exact
On Tue, Dec 18, 2012 at 6:55 AM, Junio C Hamano wrote:
> Sitaram Chamarty writes:
>
>> When using -M with a number to act as a threshold for declaring
>> a change as being a rename, I found a... quirk. Any 2-digit
>> number after the M will work,...
>
> That is
---
Documentation/diff-options.txt | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt
index f4f7e25..39f2c50 100644
--- a/Documentation/diff-options.txt
+++ b/Documentation/diff-options.txt
@@ -309,7 +309,11 @@ e
it log -1 --stat --raw -M100
# but this shows it like a rename
git log -1 --stat --raw -M100%
# adding a percent sign fixes it, now they're two separate
# files. It seems to be required only when you ask for 100%
--
Sitaram Chamarty
--
To unsubscribe from this list: send the
On Tue, Dec 11, 2012 at 11:14 AM, Patrick Donnelly wrote:
> Sorry I'm late to this party...
>
> I'm an Nmap developer that is casually interested in git development.
> I've been lurking for a while and thought I'd post my thoughts on this
> thread.
>
> On Sun, Nov 25, 2012 at 6:25 AM, Nguyen Thai
On Sun, Dec 2, 2012 at 3:01 PM, Junio C Hamano wrote:
> Sitaram Chamarty writes:
>
>> If I could assume that a successful 'git gc' means an fsck is not
>> needed, I'd save a lot of time. Hence my question.
>
> When it does "repack -a", it at lea
On Sun, Dec 2, 2012 at 9:58 AM, Shawn Pearce wrote:
> On Sat, Dec 1, 2012 at 6:31 PM, Sitaram Chamarty wrote:
>> Background: I have a situation where I have to fix up a few hundred
>> repos in terms of 'git gc' (the auto gc seems to have failed in many
>> case
On Wed, Nov 28, 2012 at 12:05 AM, Eric S. Raymond wrote:
> Magnus Bäck :
>> While "constant traffic" probably overstates the issue, these are not
>> theoretical problems. I recall at least three cases in the last year
>> or so where Git has seen breakage with Solaris or Mac OS X because
>> of sed
On Tue, Nov 27, 2012 at 1:24 PM, David Aguilar wrote:
> *cough* git-cola *cough*
>
> it runs everywhere. Yes, windows too. It's written in python.
> It's been actively maintained since 2007.
>
> It's "modern" and has features that don't exist anywhere else.
>
> It even has tests. It even comes
On Mon, Nov 26, 2012 at 4:17 AM, Eric S. Raymond wrote:
> Krzysztof Mazur :
>> What about embedded systems? git is also useful there. C and shell is
>> everywhere, python is not.
>
> Supposing this is true (and I question it with regard to shell) if you
> tell me how you live without gitk and the
On Fri, Nov 16, 2012 at 11:34 PM, Enrico Weigelt wrote:
>
>> Provide one "main" clone which is bare, pulls automatically, and is
>> there to stay (no pruning), so that all others can use that as a
>> reliable alternates source.
>
> The problem here, IMHO, is the assumption, that the main repo will
On Thu, Nov 15, 2012 at 2:03 PM, Sitaram Chamarty wrote:
> Hi,
>
> It seems to me that whatever namespaces can do, can functionally be
> done using just a subdirectory of branches. The only real
> differences I can see are (a) a client sees less branch clutter, and
> (b) a
On Thu, Nov 15, 2012 at 7:04 AM, Andrew Ardill wrote:
> On 15 November 2012 12:15, Javier Domingo wrote:
>> Hi Andrew,
>>
>> Doing this would require I got tracked which one comes from which. So
>> it would imply some logic (and db) over it. With the hardlinking way,
>> it wouldn't require anythi
On Wed, Nov 7, 2012 at 9:24 PM, Shawn Pearce wrote:
> On Wed, Nov 7, 2012 at 7:35 AM, Josef Wolf wrote:
>> When using git-clone over an unreliable link (say, UMTS) and the network goes
>> down, git-clone deletes everything what was downloaded. When the network goes
>> up again and you restart git
On Sun, Oct 21, 2012 at 5:50 PM, Drew Northup wrote:
> On Tue, Oct 9, 2012 at 1:58 AM, Matthieu Moy
> wrote:
>> David Aguilar writes:
>>
>>> I would advise against the file locking, though. You ain't gonna need
>>> it ;-)
>>
>> What do you suggest to merge Word files?
>
> If the files are in the
On Tue, Oct 16, 2012 at 10:57 PM, Angelo Borsotti
wrote:
> Hi Andrew,
>
> one nice thing is to warn a developer that wants to modify a source
> file, that there is somebody else changing it beforehand. It is nicer
> than discovering that at push time.
Andrew:
also see http://sitaramc.github.com/
On Sun, Oct 14, 2012 at 2:38 AM, Yi, EungJun wrote:
> Hi, all.
>
> Why git shows staging area to users, compared with the other scms hide
> it? What benefits users get?
>
> I feel staging area is useful, but it is difficult to explain why when
> someone asks me about that.
I wrote this a long tim
On Thu, Oct 11, 2012 at 11:08 PM, Jim Vahl wrote:
> Drew,
>
> Thanks for responding to my email!
>
> Yes, I did read most of the Book, although I admit that I skimmed over some
> of the more technical parts. There is still a key part of how git is used
> in a commercial environment which I don't
On Tue, Oct 9, 2012 at 10:53 PM, Bogdan Cristea wrote:
> I have already posted this message on git-us...@googlegroups.com but I have
> been
> advised to rather use this list. I know that there is a related thread
> (http://thread.gmane.org/gmane.comp.version-control.git/207257), but I don't
> thi
oops; forgot to add the git list earlier.
-- Forwarded message --
From: Sitaram Chamarty
Date: Wed, Oct 10, 2012 at 5:15 AM
Subject: potential path traversal issue in v3 with wild repos
To: gitolite , gitolite-annou...@googlegroups.com
Cc: Stephane Chazelas
Hello all,
I&#
On Fri, Oct 5, 2012 at 7:05 AM, demerphq wrote:
> On 5 October 2012 03:00, Andrew Ardill wrote:
>> On 5 October 2012 07:20, Marco Craveiro wrote:
>>> ...
>>> Similar but not quite; the idea is that you know that there is some
>>> code (I'm just talking about files here, so lets ignore hunks for
On Tue, Sep 11, 2012 at 4:47 PM, Joachim Schmitz
wrote:
> Like this?
> git pull --rebase HEAD~42
>
> So far I create patches, wiped out the entire repository, cloned, forked and
> applied the changes, pretty painful.
I think a 'git pull --rebase' should usually work even for 'pu'.
But sometime
On Mon, Sep 3, 2012 at 7:38 PM, Konstantin Khomoutov
wrote:
> On Mon, 3 Sep 2012 14:07:48 +0100 (BST)
> Mark Hills wrote:
>
> [...]
>> > But I'm actually more curious about why you need this in the first
>> > place, there's a bunch of devs where I work as well, but they never
>> > have the need t
On Mon, Sep 3, 2012 at 6:45 PM, Mark Hills wrote:
> On Mon, 3 Sep 2012, Sitaram Chamarty wrote:
>
>> On Mon, Sep 3, 2012 at 5:17 PM, Konstantin Khomoutov
>> wrote:
>> > On Mon, 3 Sep 2012 11:21:43 +0100 (BST)
>> > Mark Hills wrote:
>>
>> [snip]
&g
1 - 100 of 118 matches
Mail list logo
