On Sat, 2015-03-28 at 19:52 +0100, Torsten Bögershausen wrote:
> As you only push to "new", "new" should have no information about
> "old" or "temp".
Exactly, that would be the goal.
> > 1) Is it working like I assumed above?
> > 2) Does that also copy things like git-config, hooks, etc.?
> > 3
On Sat, 2015-03-28 at 15:31 +0100, Kevin D wrote:
> What you are losing on clone is:
> * config settings (this includes the configures remotes)
> * hooks
that would be okay...
> * reflog (history of refs, though, by default disabled for bare
> repositories)
is there a way to get this copied?
Hey.
I was looking for an ideally simple way to make a "full" copy of a git
repo. Many howtos are floating around on this on the web, with also lots
of voodoo.
First, it shouldn't be just a clone, i.o.w.
- I want to have all refs (local/remote branches/tags) and of course all
objects from the so
Hi.
I was converting some very old svn repos of mine into git using git svn,
and since I didn't fully trust the conversion process I wrote a small
tool which goes through all commits/revisions (there were no branches or
non-linear stuff involved in these svn repos) and compares the author
names, d
Hey.
Short question:
I saw that when plain git (i.e. git://) is used, the client tells the
server the hostname specified on the client side.
For http one has the same automatically via http's Host: header.
But after watching the git's over-ssh protocol, I couldn't find anything
like that there?
On Tue, 2015-02-24 at 10:29 -0800, Junio C Hamano wrote:
> Hmm, but if it does not, wouldn't that countermand the wish of the
> user who explicitly asked to clean crufty messages up by setting
> their own commit.cleanup configuration?
IMHO it's just wrong behaviour if the commit messages of peopl
On Mon, 2015-02-23 at 09:21 +0100, Dennis Kaarsemaker wrote:
> It used to be for a brief period in history, between daa22c6f8d (2.1.0)
> and 1f32ecf (2.2.2).
Ah thanks,... I have 2.1.4 which explains this :)
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Hey.
Right now, all --cleanup modes for commit (except verbatim) seem to
remove all "unnecessary" whitespace and collapse consecutive empty
lines.
I use already vim to show me any such things and when I don't remove it
then, this usually means I want to have it intentionally (especially
consecuti
Hey.
Just a question about files like:
.git/config
.git/hooks/*.sample
Is there any reason that these are created executable? Especially the
config file?
I know the hooks are already disabled by being named .sample, but having
them executable just increases the chance that one accidentally fires
Hey.
When I do a simple interactive rebase, e.g. something like this:
edit 78f3ba8 editing or just rewriting this commit
pick b621076 foo
pick e06c28e this one had a "verbatim" commit message
pick c0a447f bar
and one of the commit messages from the children I edit/rewrite had a
commit message tha
Hi.
Apparently since a while, git difftool has the awseome feature,
that it just symlinks the files to the working copy, if a diff with
that is requested.
e.g. something like:
git difftool -d
will have
/tmp/git-difftool.TWYTA
created with subdirs
left:
-rw-r--r-- 1 user user 45k Oct 1
Hi John.
On Wed, 2013-03-27 at 23:07 +, John Keeping wrote:
> That's not going to work well on Windows, is it?
Uhm Winwhat? No seriously... doesn't dir-diff fail ther anway? The mkdir
right now also uses mkpath with "/"... and I could read in it's
documentation that it would automatically tr
uld be forbidden, but just to be
save from collisions, any occurance of a backslash \ is replaced by a
backslash followed by an underscore \_ at first.
* Use this new function to construct the pathnames of the temporary directories
for the two revisions in dir-diffs.
Signed-off-by: Chr
On Sat, 2013-03-23 at 12:36 +, John Keeping wrote:
> > What do you all think about something like the output of
> > "git describe --always" instead of the SHA-1?
> I think Christoph was suggesting that it should use the revision as
> specified by the user, presumably falling back to HEAD when o
Hi.
Right now, when I use difftool --dir-diff, the temp dirs are creates as
e.g.:
/tmp/git-difftool.QqP8x/left
/tmp/git-difftool.QqP8x/right
Wouldn't it be nice, if instead of left/right... the specified commit
name would be used?
e.g.
/tmp/git-difftool.QqP8x/r1.1.1
/tmp/git-difftool.QqP8x/HEAD
15 matches
Mail list logo
