FW: GIT Support Partners

[Scott Sobstad]

Hi- I'm wondering if anyone could suggest a GIT support partner(s)?  The 
community is great, but I'm looking for a more personalized GIT support 
experience.  

Thanks!

-Scott Sobstad

Scott Sobstad
Director-Application Support,TSG
JDA Software
20700 Swenson Dr,
Waukesha, WI 53186 / United States
1.262.317.2185 / office
1.480.308.3000 / worldwide
scott.sobs...@jda.com
visit us / jda.com 

Fw: [git-users] git fsck error - duplicate file entries - different then existing stackoverflow scenarios

[Konstantin Khomoutov]

A user recently asked an interesting question on the git-users list.
I think it warrants attentions of a specialists more hard-core than
we're there over at git-users.

So I'd like to solicit help if those knowledgeable, if possible.

Begin forwarded message:

Date: Wed, 11 Nov 2015 14:30:40 -0800 (PST)
From: Wind Over Water 
To: Git for human beings 
Subject: [git-users] git fsck error - duplicate file entries -
different then existing stackoverflow scenarios


Hi all,

I have a repo that is giving a 'git fsck --full' error that seems to be 
different from the existing questions and answers on stackoverflow on
this topic.  For example, in our fsck error it is not obvious which
file is actually duplicated and how/where.  And there is no commit sha
involved - apparently only blob and tree sha's.  But then finding good
documentation on this is challenging.

Might anyone have a pointer as to what to read to help figure out a 
solution/fix to the below?  Or know of a solution outright?

Thanks much in advance!

-sandy

$ git fsck --full

Checking object directories: 100% (256/256), done.

error in tree df79068051fa8702eae7e91635cca7eee1339002: contains
duplicate file entries

error in tree c2d09540a3c3f44c42be1dc8a2b0afa73a35f861: contains
duplicate file entries

Checking objects: 100% (623704/623704), done.

Checking connectivity: 623532, done.

dangling commit 4d1402c8c74c9f4de6172d7dbd5a14c41683c9e8


$ git ls-tree df79068051fa8702eae7e91635cca7eee1339002

100644 blob 14d6d1a6a2f4a7db4e410583c2893d24cb587766 build.gradle

12 blob cd70e37500a35663957cf60f011f81703be5d032 msrc

04 tree 658c892e15fbe0d3ea6b8490d9d54c5f2e658fc9 msrc

100644 blob f623819c94a08252298220871ac0ba1118372e59 pom.xml

100644 blob 9223cc2fddb138f691312c1ea2656b9dc17612d2 settings.gradle

04 tree c3bac1d92722bdee9588a27747b164baa275201f src


$ git ls-tree c2d09540a3c3f44c42be1dc8a2b0afa73a35f861

100644 blob 14d6d1a6a2f4a7db4e410583c2893d24cb587766 build.gradle

12 blob cd70e37500a35663957cf60f011f81703be5d032 msrc

04 tree 658c892e15fbe0d3ea6b8490d9d54c5f2e658fc9 msrc

100644 blob f623819c94a08252298220871ac0ba1118372e59 pom.xml

100644 blob 9223cc2fddb138f691312c1ea2656b9dc17612d2 settings.gradle

04 tree a5aa6758a25fee779cbb8c9717d744297071ea79 src


$ git show cd70e37500a35663957cf60f011f81703be5d032

src/main/java/com/foo/bar/baz/common/


$ git show 658c892e15fbe0d3ea6b8490d9d54c5f2e658fc9

tree 658c892e15fbe0d3ea6b8490d9d54c5f2e658fc9


BillingAggregator.java

BillingDataThriftAdapter.java

[...]

MetricsProcessor.java
--
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: Fw: [git-users] git fsck error - duplicate file entries - different then existing stackoverflow scenarios

[Jeff King]

On Thu, Nov 12, 2015 at 02:02:10PM +0300, Konstantin Khomoutov wrote:

> A user recently asked an interesting question on the git-users list.
> I think it warrants attentions of a specialists more hard-core than
> we're there over at git-users.
> 
> So I'd like to solicit help if those knowledgeable, if possible.

Thanks. Curating user questions and forwarding the hard ones here is
appreciated.

> I have a repo that is giving a 'git fsck --full' error that seems to be 
> different from the existing questions and answers on stackoverflow on
> this topic.  For example, in our fsck error it is not obvious which
> file is actually duplicated and how/where.  And there is no commit sha
> involved - apparently only blob and tree sha's.  But then finding good
> documentation on this is challenging.

Yes, fsck does not traverse the graph in order. So it sees a problem
with a particular tree, but cannot know where that tree is within the
whole project tree, or which commits reference it. In fact, an arbitrary
number of commits might reference it.

The most useful thing is sometimes to ask which commit introduced the
tree (which can _also_ have multiple answers, but usually just one). You
can do that by walking the history, like this:

  tree=df79068051fa8702eae7e91635cca7eee1339002
  git log --all --format=raw --raw -t --no-abbrev | less +/$tree

That will visit each commit. The options are:

  - we visit commits reachable from all branches and tags (--all)

  - we include the sha1 of the root tree (due to --format=raw)

  - adding --raw shows the raw diff, which includes the sha1 of each
file touched by the commit

  - using "-t" includes the raw diff for trees, rather than just blobs

  - using "--no-abbrev" gives full 40-hex sha1s

And then "less +/$tree" will open the pager and immediately jump to the
first instance of the sha1 in question.

But of course that doesn't tell you how to fix it. It might tell you how
the bogus object came about (and it is a bogus object; a bug-free git
implementation should _never_ produce a tree with duplicate entries.
AFAIK we have never had such a bug in Git itself, but I have
occasionally come across problematic entries that I suspect were created
with very old versions of JGit).

> error in tree df79068051fa8702eae7e91635cca7eee1339002: contains
> duplicate file entries
> [...]
> $ git ls-tree df79068051fa8702eae7e91635cca7eee1339002
> 
> 100644 blob 14d6d1a6a2f4a7db4e410583c2893d24cb587766 build.gradle
> 
> 12 blob cd70e37500a35663957cf60f011f81703be5d032 msrc
> 
> 04 tree 658c892e15fbe0d3ea6b8490d9d54c5f2e658fc9 msrc
> 
> 100644 blob f623819c94a08252298220871ac0ba1118372e59 pom.xml
> 
> 100644 blob 9223cc2fddb138f691312c1ea2656b9dc17612d2 settings.gradle
> 
> 04 tree c3bac1d92722bdee9588a27747b164baa275201f src

Looks like "msrc" is your duplicate entry (even though the sha1s of the
sub-entries are different, the tree cannot have two entries with the
same name). You can use the "log" trick above to find the full path to it.

The fact that one is a symlink (mode 12) and one is a tree means
that whatever git implementation created this presumably has a bug
related to symlinks.

The only way to fix it is to rewrite the history mentioning the tree
(because once the tree is fixed, it will get a new sha1, and then any
commit referencing it will get a new sha1, and commits built on that,
and so forth).

You can use "git filter-branch" to do so. There is a sample command
here:

  
http://stackoverflow.com/questions/32577974/duplicate-file-error-while-pushing-mirror-into-git-repository/

that just rewrites each tree via a round-trip to the index (so it's not
clear which of the duplicate entries it will discard). You could also
write a more clever index-filter snippet to use git-update-index to
insert the entry you want.

-Peff
--
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

FW: Git crash in windows 2012 R2

[Fran Mico]

Hi,

My name is Fran, we are a development team who uses git. We have our 
Development Environment in the server office (Windows 2008 R2) where everything 
runs without problems. We are planning to move to Windows Azure so we bought a 
virtual server to try our Development Environment and check the performance and 
if we will be able to do everything we are doing at the moment in the office 
server in the virtual server (Windows Azure).

We came across with a problem when installing Git in the Virtual server (Window 
Azure - Windows 2012 R2 64bits)

All the installation process went ok (except once that it didn't finished, the 
only thing missing was the Environment Variable that I had to introduce 
manually) , the only problem is that when we run in the Window Command Prompt 
the command 'git' the command prompt crashes and do not respond anymore.

This is the installation options we have tried:

First installation (Git 1.9.2)
Windows Explorer integration (Advanced context menu git-cheetah plugin)
Use Git from the Windows Command Prompt
Second installation (Git 1.9.2)
Windows Explorer integration (Git Bash Here, Git GUI Here)
Use Git from the Windows command prompt
Third installation (Portable Git 1.9.0)
We have try as well downloading the portable version and setting the 
Environment variables

All the installations cause the same behaviour in the command prompt when 
running the command 'git' on it

If you need any more information (screenshoots...) that could be useful for 
you, let me know and I will send it over.

Many thanks.

Kind regards,
Fran Mico
--
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: FW: Git log --graph doesn't output color when redirected

[Junio C Hamano]

Jeff King p...@peff.net writes:

 On Sat, Dec 15, 2012 at 10:23:10AM +0700, Nguyen Thai Ngoc Duy wrote:

 On Thu, Dec 13, 2012 at 8:13 PM, Jeff King p...@peff.net wrote:
  If you are using --format=%C(red) or similar placeholders,
  they are the odd duck by not respecting the auto-color mode.
 
 But they should, shouldn't they? Just asking. I may do it to when I
 revive nd/pretty-placeholder-with-color-option.

 If I were designing --format today, I would certainly say so. The only
 thing holding me back would be backwards compatibility. We could get
 around that by introducing a new placeholder like %c(color) that behaves
 like %C(color), except respects the --color flag.

I think the %c(color) thing is a good way to go if we want to pursue
this.

Another possibility without wasting one more special letter would be
to allow %C(auto,red), perhaps like this (untested):

 pretty.c | 13 ++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git i/pretty.c w/pretty.c
index dba6828..77cf826 100644
--- i/pretty.c
+++ w/pretty.c
@@ -960,12 +960,19 @@ static size_t format_commit_one(struct strbuf *sb, const 
char *placeholder,
switch (placeholder[0]) {
case 'C':
if (placeholder[1] == '(') {
-   const char *end = strchr(placeholder + 2, ')');
+   const char *begin = placeholder + 2;
+   const char *end = strchr(begin, ')');
char color[COLOR_MAXLEN];
+
if (!end)
return 0;
-   color_parse_mem(placeholder + 2,
-   end - (placeholder + 2),
+   if (!memcmp(begin, auto,, 5)) {
+   if (!want_color(GIT_COLOR_AUTO))
+   return 0;
+   begin += 5;
+   }
+   color_parse_mem(begin,
+   end - begin,
--pretty format, color);
strbuf_addstr(sb, color);
return end - placeholder + 1;
--
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: FW: Git log --graph doesn't output color when redirected

[Nguyen Thai Ngoc Duy]

On Thu, Dec 13, 2012 at 8:13 PM, Jeff King p...@peff.net wrote:
 If you are using --format=%C(red) or similar placeholders,
 they are the odd duck by not respecting the auto-color mode.

But they should, shouldn't they? Just asking. I may do it to when I
revive nd/pretty-placeholder-with-color-option.
-- 
Duy
--
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: FW: Git log --graph doesn't output color when redirected

[Jeff King]

On Wed, Dec 12, 2012 at 05:35:17PM +, Srb, Michal wrote:

 Unlike --pretty-format, --graph doesn’t output colors when the git log output
 is redirected.

I do not think it has anything to do with --graph in particular, but
rather that when colorization is set to the auto mode, it is enabled
only when stdout is a tty. Diff coloring, for example, follows the same
rules.  If you are using --format=%C(red) or similar placeholders,
they are the odd duck by not respecting the auto-color mode.

 Is there a setting somewhere in config to change this?

Yes. If you use --color on the command line, that means
unconditionally use color. If you set color.ui (or any other color
config option) to always, then you will always get color (and you can
disable it for a particular run with --no-color). Setting a color
config option to true is the same as auto, which gets you the auto
mode.

-Peff
--
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: FW: Git log --graph doesn't output color when redirected

[Srb, Michal]

From: Jeff King [p...@peff.net]
Sent: Thursday, December 13, 2012 1:13 PM

 Is there a setting somewhere in config to change this?

 Yes. If you use --color on the command line, that means
 unconditionally use color. If you set color.ui (or any other
 color config option) to always, then you will always get color (and
 you can disable it for a particular run with --no-color). Setting a color
 config option to true is the same as auto, which gets you 
 the auto mode.
 
Setting color in gitconfig didn't work for me on msys, but --color 
works like magic, 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

FW: Git log --graph doesn't output color when redirected

[Srb, Michal]

Unlike --pretty-format, --graph doesn’t output colors when the git log output
is redirected.
 
Tested on Ubuntu 12.04 and msys on Windows 8.
 
Is there a setting somewhere in config to change this?
 
Thanks,
 
Michal





--
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: Fw: [git-users] How do I git-push to an FTP server?

[Ramkumar Ramachandra]

Junio C Hamano wrote:
 Jonathan Nieder jrnie...@gmail.com writes:

 Ramkumar Ramachandra wrote:
 Thomas Ferris Nicolaisen tfn...@gmail.com writes:

 At least according to the documentation[1], Git natively supports [...] 
 ftp.

 This could need some clarification if pushing over ftp is not supported.
 [...]
 -Git natively supports ssh, git, http, https, ftp, ftps, and rsync
 -protocols. The following syntaxes may be used with them:
 +Git natively supports ssh, git, http, https, and rsync protocols. The
 +following syntaxes may be used with them:

 Perhaps the initial list should not be exhaustive, in which case we
 could say:

   Git natively supports ssh, git, http, and https protocols.  The
   following syntaxes may be used with them:

   ...

   Git also has (less efficient) support for fetching and pushing
   over rsync protocol and fetching over ftp or ftps, using the
   same protocol://host/path/to/repo.git/ syntax.

 Yeah, that, possibly with These are deprecated; do not use them.,
 would be a better way forward.  As we deprecated rsync long time
 ago, perhaps we should remove it at Git 2.0 or somewhere around
 that.

I see.  Will we remove ftp[s] support too?  I hope this is in order.

-- 8 --
From: Ramkumar Ramachandra artag...@gmail.com
Date: Sun, 7 Oct 2012 20:57:15 +0530
Subject: [PATCH] Documentation/urls: mark rsync and ftp[s] as deprecated

Fetching and pushing over rsync, and fetching over ftp or ftps are
deprecated, and will soon be removed.  Add a note saying this.

Helped-by: Jonathan Nieder jrnie...@gmail.com
Signed-off-by: Ramkumar Ramachandra artag...@gmail.com
---
 Documentation/urls.txt | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index 2890194..653b61c 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -6,14 +6,12 @@ address of the remote server, and the path to the repository.
 Depending on the transport protocol, some of this information may be
 absent.

-Git natively supports ssh, git, http, https, ftp, ftps, and rsync
-protocols. The following syntaxes may be used with them:
+Git natively supports ssh, git, http, and https protocols. The
+following syntaxes may be used with them:

 - ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/
 - git://host.xz{startsb}:port{endsb}/path/to/repo.git/
 - http{startsb}s{endsb}://host.xz{startsb}:port{endsb}/path/to/repo.git/
-- ftp{startsb}s{endsb}://host.xz{startsb}:port{endsb}/path/to/repo.git/
-- rsync://host.xz/path/to/repo.git/

 An alternative scp-like syntax may also be used with the ssh protocol:

@@ -31,6 +29,11 @@ syntaxes may be used:
 - /path/to/repo.git/
 - file:///path/to/repo.git/

+ Git also has (less efficient) support for fetching and pushing over
+ rsync protocol and fetching over ftp or ftps, using the same
+ protocol://host/path/to/repo.git/ syntax.  However, these are
+ deprecated, and will soon be removed.
+
 ifndef::git-clone[]
 These two syntaxes are mostly equivalent, except when cloning, when
 the former implies --local option. See linkgit:git-clone[1] for
-- 
1.7.12.1.428.g652398a.dirty
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Jonathan Nieder]

Ramkumar Ramachandra wrote:

 I see.  Will we remove ftp[s] support too?  I hope this is in order.

I don't see why that would be desirable, as long as libcurl continues
to support it for free.

[...]
 Fetching and pushing over rsync, and fetching over ftp or ftps are
 deprecated, and will soon be removed.  Add a note saying this.

I thought the real rationale was to avoid creating the illusion of
supporting push over ftp.  Having a paper trail to comfort people who
notice when rsync support vanishes is just an added bonus.

[...]
 @@ -31,6 +29,11 @@ syntaxes may be used:
  - /path/to/repo.git/
  - file:///path/to/repo.git/
 
 + Git also has (less efficient) support for fetching and pushing over
 + rsync protocol and fetching over ftp or ftps, using the same
 + protocol://host/path/to/repo.git/ syntax.  However, these are
 + deprecated, and will soon be removed.

I'd suggest dropping , and will soon be removed. or replacing it
with . Don't use them. to avoid the question of how soon soon is.

With that change and with a clearer commit message, this will probably
be good to go imho.

Thanks,
Jonathan
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Junio C Hamano]

Jonathan Nieder jrnie...@gmail.com writes:

 I'd suggest dropping , and will soon be removed. or replacing it
 with . Don't use them. to avoid the question of how soon soon is.

 With that change and with a clearer commit message, this will probably
 be good to go imho.

Yup; 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

Re: Fw: [git-users] How do I git-push to an FTP server?

[Junio C Hamano]

Junio C Hamano gits...@pobox.com writes:

 Jonathan Nieder jrnie...@gmail.com writes:

 I'd suggest dropping , and will soon be removed. or replacing it
 with . Don't use them. to avoid the question of how soon soon is.

 With that change and with a clearer commit message, this will probably
 be good to go imho.

 Yup; thanks.

Let's do this, then.

-- 8 --
From: Ramkumar Ramachandra artag...@gmail.com
Subject: Git url doc: mark ftp/ftps as read-only and deprecate them

It is not even worth mentioning their removal; just discourage
people from using them.

Signed-off-by: Ramkumar Ramachandra artag...@gmail.com
Helped-by: Jonathan Nieder jrnie...@gmail.com
Signed-off-by: Junio C Hamano gits...@pobox.com
---
 Documentation/urls.txt | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git i/Documentation/urls.txt w/Documentation/urls.txt
index 2890194..1d15ee7 100644
--- i/Documentation/urls.txt
+++ w/Documentation/urls.txt
@@ -6,8 +6,12 @@ address of the remote server, and the path to the repository.
 Depending on the transport protocol, some of this information may be
 absent.
 
-Git natively supports ssh, git, http, https, ftp, ftps, and rsync
-protocols. The following syntaxes may be used with them:
+Git supports ssh, git, http, and https protocols (in addition, ftp,
+and ftps can be used for fetching and rsync can be used for fetching
+and pushing, but these are inefficient and deprecated; do not use
+them).
+
+The following syntaxes may be used with them:
 
 - ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/
 - git://host.xz{startsb}:port{endsb}/path/to/repo.git/
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Jonathan Nieder]

Junio C Hamano wrote:

 Let's do this, then.

I think it would be nicer to start with the important info (git
supports ssh, git, http, https) and deal with less important parts
like rsync support later in the document, but this looks like a good
minimal fix.  Thanks for pushing it to completion.

For what it's worth,
Reviewed-by: Jonathan Nieder jrnie...@gmail.com
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Junio C Hamano]

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

Re: Fw: [git-users] How do I git-push to an FTP server?

[Ramkumar Ramachandra]

Junio C Hamano wrote:
 Thomas Ferris Nicolaisen tfn...@gmail.com writes:

 On Fri, Oct 5, 2012 at 3:46 PM, Philippe Vaucher
 philippe.vauc...@gmail.com wrote:

  On the git-users mailing list we're trying someone to help with
  running `git push` over FTP.  That person is runnig Git 1.7.9.5
  on Ubuntu 12.04.

 I don't think vanilla git supports pushing over ftp.


 At least according to the documentation[1], Git natively supports [...] 
 ftp.

 This could need some clarification if pushing over ftp is not supported.

 The commit 5ce4f4e (Documentation/urls: Rewrite to accomodate
 transport::address, 2010-04-06) that came from

   http://thread.gmane.org/gmane.comp.version-control.git/145196/focus=145205

 was supposed to be just a clarification of the document, but it
 added ftp to the list without justification.

Hm, my bad.  Would this fix the problem?

-- 8 --
From: Ramkumar Ramachandra artag...@gmail.com
Date: Sun, 7 Oct 2012 20:57:15 +0530
Subject: [PATCH] Documentation/urls: git does not natively support ftp

5ce4f4e (Documentation/urls: Rewrite to accomodate
transport::address, 2010-04-06) added ftp[s] to the list of
supported protocols without justification.  Fix this.

Signed-off-by: Ramkumar Ramachandra artag...@gmail.com
---
 Documentation/urls.txt | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index 2890194..a65e894 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -6,13 +6,12 @@ address of the remote server, and the path to the repository.
 Depending on the transport protocol, some of this information may be
 absent.

-Git natively supports ssh, git, http, https, ftp, ftps, and rsync
-protocols. The following syntaxes may be used with them:
+Git natively supports ssh, git, http, https, and rsync protocols. The
+following syntaxes may be used with them:

 - ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/
 - git://host.xz{startsb}:port{endsb}/path/to/repo.git/
 - http{startsb}s{endsb}://host.xz{startsb}:port{endsb}/path/to/repo.git/
-- ftp{startsb}s{endsb}://host.xz{startsb}:port{endsb}/path/to/repo.git/
 - rsync://host.xz/path/to/repo.git/

 An alternative scp-like syntax may also be used with the ssh protocol:
-- 
1.7.12.1.428.g652398a.dirty
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Jonathan Nieder]

Ramkumar Ramachandra wrote:
 Thomas Ferris Nicolaisen tfn...@gmail.com writes:

 At least according to the documentation[1], Git natively supports [...] 
 ftp.

 This could need some clarification if pushing over ftp is not supported.
[...]
 -Git natively supports ssh, git, http, https, ftp, ftps, and rsync
 -protocols. The following syntaxes may be used with them:
 +Git natively supports ssh, git, http, https, and rsync protocols. The
 +following syntaxes may be used with them:

Perhaps the initial list should not be exhaustive, in which case we
could say:

Git natively supports ssh, git, http, and https protocols.  The
following syntaxes may be used with them:

...

Git also has (less efficient) support for fetching and pushing
over rsync protocol and fetching over ftp or ftps, using the
same protocol://host/path/to/repo.git/ syntax.
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Junio C Hamano]

Jonathan Nieder jrnie...@gmail.com writes:

 Ramkumar Ramachandra wrote:
 Thomas Ferris Nicolaisen tfn...@gmail.com writes:

 At least according to the documentation[1], Git natively supports [...] 
 ftp.

 This could need some clarification if pushing over ftp is not supported.
 [...]
 -Git natively supports ssh, git, http, https, ftp, ftps, and rsync
 -protocols. The following syntaxes may be used with them:
 +Git natively supports ssh, git, http, https, and rsync protocols. The
 +following syntaxes may be used with them:

 Perhaps the initial list should not be exhaustive, in which case we
 could say:

   Git natively supports ssh, git, http, and https protocols.  The
   following syntaxes may be used with them:

   ...

   Git also has (less efficient) support for fetching and pushing
   over rsync protocol and fetching over ftp or ftps, using the
   same protocol://host/path/to/repo.git/ syntax.

Yeah, that, possibly with These are deprecated; do not use them.,
would be a better way forward.  As we deprecated rsync long time
ago, perhaps we should remove it at Git 2.0 or somewhere around
that.

By the way, that old patch by Ram in question was *not* incorrect
per-se back then when dumb http was still more prevalent option
between the two http transports.  Fetching over dumb http and dumb
ftp were both equally bad ;-)  It just has become less relevant as
more people start equating http with the smart http, where there is
no equivalent smart ftp.
--
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

Fw: [git-users] How do I git-push to an FTP server?

[Konstantin Khomoutov]

On the git-users mailing list we're trying someone to help with
running `git push` over FTP.  That person is runnig Git 1.7.9.5
on Ubuntu 12.04.

Below is the trace captured while trying to perform such a faulty push.
The oddity (in my eyes) is that after uploading the files, Git executes
`git http-push` which manual page does not mention FTP at all.

So I'd like to ask experts on Git transports for any advice in this
situation.

Begin forwarded message:

Date: Fri, 5 Oct 2012 05:07:24 -0700 (PDT)
From: August Karlstrom fusio...@gmail.com
To: git...@googlegroups.com
Cc: August Karlstrom fusio...@gmail.com
Subject: Re: [git-users] How do I git-push to an FTP server?

Den fredagen den 5:e oktober 2012 kl. 11:38:43 UTC+2 skrev Konstantin 
Khomoutov:

 On Fri, 5 Oct 2012 01:24:21 -0700 (PDT) 
 August Karlstrom fusio...@gmail.com javascript: wrote: 

  I get the following error when I run `git push' in a repository 
  called test: 
  
  error: Cannot access URL ftp://my-ftp-server/git/test.git/, return 
  code 3 fatal: git-http-push failed 
  
  This is after having successfully cloned the repository from the 
  address above. 
 Try to run your command while having set GIT_TRACE=1 and 
 GIT_CURL_VERBOSE=1, like 

 $ GIT_TRACE=1 GIT_CURL_VERBOSE=1 git push 

 and post the results here (if you will fail to infer the cause from
 its output by yourself). 


Thanks for the input, Konstantin. Below is the output (with identifying 
info removed). I can't see what caused Uploading to a URL without a
file name at the end.

$ GIT_TRACE=1 GIT_CURL_VERBOSE=1 git push
trace: built-in: git 'push'
trace: run_command: 'git-remote-ftp' 'origin' 
'ftp://my-ftp-server/git/test.git'
* About to connect() to my-ftp-server port 21 (#0)
*   Trying my-ftp-ip... * Connected to my-ftp-server (my-ftp-ip) port
21 (#0)
 220-- Welcome to Pure-FTPd [privsep] [TLS] -- 
 220-You are user number 6 of 400 allowed. 
 220-Local time is now 11:23. Server port: 21. 
 220-This is a private system - No anonymous login 
 220 You will be disconnected after 15 minutes of inactivity. 
 USER my-username 
 331 User my-username OK. Password required 
 PASS my-password 
 230-User my-username has group access to:  my-group 
 230 OK. Current restricted directory is / 
 PWD 
 257 / is your current location 
* Entry path is '/'
 CWD git 
 250 OK. Current directory is /git 
 CWD test.git 
 250 OK. Current directory is /git/test.git 
 CWD info 
 250 OK. Current directory is /git/test.git/info 
 EPSV 
* Connect data stream passively
 500 Unknown command 
* disabling EPSV usage
 PASV 
 227 Entering Passive Mode ([not shown]) 
*   Trying my-ftp-ip... * Connecting to my-ftp-ip (my-ftp-ip) port 63983
 TYPE I 
 200 TYPE is now 8-bit binary 
 SIZE refs 
 213 59 
 RETR refs 
 150 Accepted data connection 
* Maxdownload = -1
* Getting file with size: 59
* Remembering we are in dir git/test.git/info/
 226-File successfully transferred 
 226 0.000 seconds (measured here), 1.34 Mbytes per second 
* Connection #0 to host my-ftp-server left intact
* Re-using existing connection! (#0) with host my-ftp-server
* Connected to my-ftp-server (my-ftp-ip) port 21 (#0)
 CWD / 
 250 OK. Current directory is / 
 CWD git 
 250 OK. Current directory is /git 
 CWD test.git 
 250 OK. Current directory is /git/test.git 
 PASV 
* Connect data stream passively
 227 Entering Passive Mode ([not shown]) 
*   Trying my-ftp-ip... * Connecting to my-ftp-ip (my-ftp-ip) port 63462
 SIZE HEAD 
 213 23 
 RETR HEAD 
 150 Accepted data connection 
* Maxdownload = -1
* Getting file with size: 23
* Remembering we are in dir git/test.git/
 226-File successfully transferred 
 226 0.000 seconds (measured here), 0.63 Mbytes per second 
* Connection #0 to host my-ftp-server left intact
trace: run_command: 'http-push' '--helper-status' 
'ftp://my-ftp-server/git/test.git/'
'refs/heads/master:refs/heads/master' trace: exec: 'git' 'http-push'
'--helper-status' 'ftp://my-ftp-server/git/test.git/'
'refs/heads/master:refs/heads/master' trace: exec: 'git-http-push'
'--helper-status' 'ftp://my-ftp-server/git/test.git/'
'refs/heads/master:refs/heads/master' trace: run_command:
'git-http-push' '--helper-status' 'ftp://my-ftp-server/git/test.git/'
'refs/heads/master:refs/heads/master'
* About to connect() to my-ftp-server port 21 (#0)
*   Trying my-ftp-ip... * Connected to my-ftp-server (my-ftp-ip) port
21 (#0)
 220-- Welcome to Pure-FTPd [privsep] [TLS] -- 
 220-You are user number 7 of 400 allowed. 
 220-Local time is now 11:23. Server port: 21. 
 220-This is a private system - No anonymous login 
 220 You will be disconnected after 15 minutes of inactivity. 
 USER my-username 
 331 User my-username OK. Password required 
 PASS my-password 
 230-User my-username has group access to:  my-group 
 230 OK. Current restricted directory is / 
 PWD 
 257 / is your current location 
* Entry path is '/'
* Uploading to a URL without a file name!
* Closing connection #0
error: Cannot access URL 

Re: Fw: [git-users] How do I git-push to an FTP server?

[Philippe Vaucher]

 On the git-users mailing list we're trying someone to help with
 running `git push` over FTP.  That person is runnig Git 1.7.9.5
 on Ubuntu 12.04.

I don't think vanilla git supports pushing over ftp.

There are plugins like https://github.com/resmo/git-ftp tho.

Philippe
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Thomas Ferris Nicolaisen]

On Fri, Oct 5, 2012 at 3:46 PM, Philippe Vaucher
philippe.vauc...@gmail.com wrote:

  On the git-users mailing list we're trying someone to help with
  running `git push` over FTP.  That person is runnig Git 1.7.9.5
  on Ubuntu 12.04.

 I don't think vanilla git supports pushing over ftp.


At least according to the documentation[1], Git natively supports [...] ftp.

This could need some clarification if pushing over ftp is not supported.

[1] http://www.kernel.org/pub/software/scm/git/docs/git-push.html#URLS
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Konstantin Khomoutov]

On Fri, 5 Oct 2012 15:46:33 +0200
Philippe Vaucher philippe.vauc...@gmail.com wrote:

  On the git-users mailing list we're trying someone to help with
  running `git push` over FTP.  That person is runnig Git 1.7.9.5
  on Ubuntu 12.04.
 
 I don't think vanilla git supports pushing over ftp.
 
 There are plugins like https://github.com/resmo/git-ftp tho.

git-ftp's functionality is completely orthogonal to `git push` -- this
script allows to sync a tree referenced by the specified Git commit
with a remote directory accessible via FTP, transferring only
new and modified files and deleting disappeared files and directories.
IOW, git-ftp is a (very handy) Git-powered *deployment* tool, not a
backend for `git push` or something like that.
--
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: Fw: [git-users] How do I git-push to an FTP server?

[Junio C Hamano]

Thomas Ferris Nicolaisen tfn...@gmail.com writes:

 On Fri, Oct 5, 2012 at 3:46 PM, Philippe Vaucher
 philippe.vauc...@gmail.com wrote:

  On the git-users mailing list we're trying someone to help with
  running `git push` over FTP.  That person is runnig Git 1.7.9.5
  on Ubuntu 12.04.

 I don't think vanilla git supports pushing over ftp.


 At least according to the documentation[1], Git natively supports [...] ftp.

 This could need some clarification if pushing over ftp is not supported.

The commit 5ce4f4e (Documentation/urls: Rewrite to accomodate
transport::address, 2010-04-06) that came from

  http://thread.gmane.org/gmane.comp.version-control.git/145196/focus=145205

was supposed to be just a clarification of the document, but it
added ftp to the list without justification.  Its earlier round is
this

http://thread.gmane.org/gmane.comp.version-control.git/143499

and it did not mention ftp; I wonder why we missed this addition
during the review process.

The ftp transport might have worked for fetching in the distant past
for dumb and slow commit walking fetches, but it was never
supposed to work with any kind of pushes as far as I know.  I
wouldn't be surprised if the dumb and slow commit walking fetch no
longer works with ftp.
--
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: FW: Git

[Drew Northup]

On Thu, 2012-08-16 at 12:47 -0600, Jean Tappan wrote:
 I am looking for a tool that will control not only versioning for
 software, but also the software's associated user and support manuals.
 I haven't been able to find anything that addresses this particular
 topic. Can you tell me about this or reference a site or page that
 discusses it?

Jean,
If you take a close look at the git.git repo itself you will notice that
several different (and at times totally non-overlapping) branches are
available. The same option is available for other projects as well.

-- 
-Drew Northup

As opposed to vegetable or mineral error?
-John Pescatore, SANS NewsBites Vol. 12 Num. 59

--
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

FW: Git

[Jean Tappan]

From: Jean Tappan 
Sent: Thursday, August 16, 2012 12:33 PM
To: 'git@vger.kernel.org'
Subject: Git

I am looking for a tool that will control not only versioning for software, but 
also the software's associated user and support manuals. I haven't been able to 
find anything that addresses this particular topic. Can you tell me about this 
or reference a site or page that discusses it?

Thank you.

Jean Tappan | Senior Technical Writer | eDOC Innovations| When Strategy Matters 
...
P:800.425.7766 x420 | F:435.657.2989 |  jtap...@edoclogic.com

Legal Notification: This e-mail and any files transmitted with it are the 
property of eDOC Innovations, Inc. and/or its affiliates, are confidential, and 
are intended solely for the use of recipient or entity to whom this e-mail is 
addressed. If you are not one of the named recipient's or otherwise have reason 
to believe that you have received this e-mail in error, please notify the 
sender and delete this message immediately from your computer. Any other use, 
retention, dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


--
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