[git-users] Re: untracked files not shown when using 'git status'

[Kurt Vermeiren]

I would agree with Matthew on this. I understand the rationale to not show 
the files because of the possible very big directories... but the 
documentation clearly states "directories and files"

On Friday, 27 November 2015 17:16:30 UTC+1, Kurt Vermeiren wrote:
>
> In our project we have 4 untracked files, for local development. 
>
> Output of *git status *:
>
> Untracked files:
>   (use "git add ..." to include in what will be committed)
>
> sdb-batch-web/src/main/webapp/WEB-INF/jboss-web.xml
> sdb-ear/src/main/application/
> sdb-services/src/main/webapp/WEB-INF/jboss-web.xml
> sdb-web/src/main/webapp/WEB-INF/jboss-web.xml
>
> Note the second line, only the directory is shown. 
>
> Output of *git status --untracked-files *:
>
> Untracked files:
>   (use "git add ..." to include in what will be committed)
>
> sdb-batch-web/src/main/webapp/WEB-INF/jboss-web.xml
> sdb-ear/src/main/application/META-INF/jboss-deployment-structure.xml
> sdb-services/src/main/webapp/WEB-INF/jboss-web.xml
> sdb-web/src/main/webapp/WEB-INF/jboss-web.xml
>
> What is the difference between both commands, our believe is the output 
> should be identical.
>
> We are on 2.6.3, OS is Ubuntu 14.04 LTS
>
> Cheers
> Kurt
>
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Create a new repo from a branch in another repo

[Konstantin Khomoutov]

On Mon, 30 Nov 2015 07:52:19 -0800 (PST)
Anthony Hunter  wrote:

> I'm new to git and looking into its usage and am responsible for the
> teams that will be using the repos.
> 
> As development goes on within a repo and time passes, the repo will
> start to get large just do to the number of commits. Is there a way
> that for example, as a release completes, I could branch off into a
> new repo to develop the next version? This will help keep the repos
> small and release specific. 
> 
> I'm aware of doing a shallow clone or even a branch clone, but I will
> still end up with users cloning the who thing by accident.

I think you're trying to overengeneer on the two fronts:

* If you want a new repo, just `git checkout` a version tagged
  as released, then `rm -rf .git` there (literally), then
  `git init .` + `git add .` + `git commit -q` and you're done.

  Since you explicitly want no history, then there's no sense in
  "branching off" -- because branching means just growing the history
  in yet another direction.

* Is the repo size *really* a concern?

  Here's why I'm asking: there are projects like Mozilla Firefox and
  Linux which contain all their histories from day one, and they
  are *huge.*  Still, Git handles them just okay.

  Sure, there's always a problem of a slow initial clone but it can
  be solved in different ways, with using "--reference" when
  `git clone`-ing being the most apparent.

  If you store some large assets in your repos, you might consider
  using tools like `git-fat`, `git-lfs` and `git-annex`.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Re: Where to start coding?

[amey jain]

Hi Konstantin Khomoutov,
Thanks that you wrote here. Yes that's right that I am new to all of it. 
Actually I want to go to GSoC and for that I started contributing to Open 
source. I am already running Ubuntu and subscribed to the mailing list of 
git to. I will for sure find some easy projects to tackle. But it was hard 
to find easy ones. Though I practice programming on C very much. I don't 
have any experience on finding projects. I think from now I will start from 
mailing lists and bug reporting in software. Thanks of you again to write 
here.  

On Monday, November 30, 2015 at 9:59:19 PM UTC+5:30, Konstantin Khomoutov 
wrote:
>
> On Sun, 29 Nov 2015 01:54:57 -0800 (PST) 
> amey jain  wrote: 
>
> > Thanks for your reply. I was working on git-scm. I have the clone of 
> > its repository. I will sure read the complete docs. I am in beginning 
> > of Open source software. Actually I wanted to know whether there are 
> > documents which tell us what function does what or what for a file is 
> > included. By the way thanks again for the answer. 
>
> Please don't perceive what I will say as a discouragement 
> but judging from these two mails of yours in this thread I'd say 
> it would be much better for you to attempt working on some more 
> accessible and simple project than Git. 
>
> "The problem" is that Git is a pretty hard-core software project 
> developed mostly by wizards -- I mean people with decades (literally) 
> of experience in writing hight-performance C code, with intricate 
> knowledge of the hardware platrofms it targets, the compilers it can be 
> built using, networking, odds of particular OSes and so on and so on. 
>
> While the project is definitely open to contribution, the way you're 
> approaching it suggests you're not such a wizard yet ;-) 
>
> I would hence do something like this instead: 
>
> * Subscribe to the main Git list [1]. 
>
> * Lurk there, and see how people discuss problems, post patches, review 
>   them and so on. 
>
>   Consider reading the archives as well [2]. 
>
> * In the meanwhile, find a project easier to tackle and play with it. 
>
>   If you have a GNU/Linux-based OS, helping out its developers with 
>   fixing outstanding bugs would be a great F/OSS experience 
>   (I maintain a pair of packages for Debian so beleive me on this) ;-) 
>
> 1. https://gist.github.com/tfnico/4441562 
> 2. http://dir.gmane.org/gmane.comp.version-control.git 
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Create a new repo from a branch in another repo

[Anthony Hunter]

Yes, my concern is with the eventual size of the repo. The repo will become 
larger then 1gig and this will take a long time to clone. Not so much 
concerned with "large files" jut the overall size of the repo.

Can you expand more on the usage of the "--reference" option?

Thanks.


>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Re: Where to start coding?

[Konstantin Khomoutov]

On Sun, 29 Nov 2015 01:54:57 -0800 (PST)
amey jain  wrote:

> Thanks for your reply. I was working on git-scm. I have the clone of
> its repository. I will sure read the complete docs. I am in beginning
> of Open source software. Actually I wanted to know whether there are
> documents which tell us what function does what or what for a file is
> included. By the way thanks again for the answer. 

Please don't perceive what I will say as a discouragement
but judging from these two mails of yours in this thread I'd say
it would be much better for you to attempt working on some more
accessible and simple project than Git.

"The problem" is that Git is a pretty hard-core software project
developed mostly by wizards -- I mean people with decades (literally)
of experience in writing hight-performance C code, with intricate
knowledge of the hardware platrofms it targets, the compilers it can be
built using, networking, odds of particular OSes and so on and so on.

While the project is definitely open to contribution, the way you're
approaching it suggests you're not such a wizard yet ;-)

I would hence do something like this instead:

* Subscribe to the main Git list [1].

* Lurk there, and see how people discuss problems, post patches, review
  them and so on.

  Consider reading the archives as well [2].

* In the meanwhile, find a project easier to tackle and play with it.

  If you have a GNU/Linux-based OS, helping out its developers with
  fixing outstanding bugs would be a great F/OSS experience
  (I maintain a pair of packages for Debian so beleive me on this) ;-)

1. https://gist.github.com/tfnico/4441562
2. http://dir.gmane.org/gmane.comp.version-control.git

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[justrajdeep]

Hi

That wont push it to the branch.

On Monday, November 30, 2015 at 3:12:06 PM UTC+5:30, Magnus Therning wrote:
>
> On Sat, Nov 28, 2015 at 06:48:35AM -0800, justrajdeep wrote: 
> > Hi 
> > 
> > I want to push my entire local repo(present only with me) to a 
> > shared git repo as a branch in that. 
> > 
> > I can do something like 
> > 
> > git remote add local-remote $PATH_TO_REPO_LOCATION 
> > git push local-remote -u master:$TREE_BRANCH 
> > 
> > But this pushes only the master. Any way to push the whole thing 
> > with all its branches and everything? 
>
> What about `git push --all`? 
>
> /M 
>
> -- 
> Magnus Therning  OpenPGP: 0xAB4DFBA4 
> email: mag...@therning.orgjabber: mag...@therning.org 
>  
> twitter: magthe   http://therning.org/magnus 
>
> Of course I laugh at my own jokes. You can't trust strangers. 
>  -- Phyllis Diller 
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[Konstantin Khomoutov]

On Mon, 30 Nov 2015 21:23:24 +0530
rajdeep mondal  wrote:

> I tried something like
> 
> git push local-remote -u 'refs/*:refs/$TREE_BRANCH/*'
> 
> it did not work as expected.

I wonder what was expected then.
To me, your invocation looks strange at best.

Can you try to explain what you want to achieve in simple words?

I mean, something like "
1) I have a repo with branches A, B and C.
2) I want to craft a command which would make branches A, B and C
   end up ... in the remote repo I intend to push them to.
"

Fill free to replace "..." in my description with something sensible.
So far, I fail to clearly understand your intent.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Re: untracked files not shown when using 'git status'

[Konstantin Khomoutov]

On Mon, 30 Nov 2015 02:00:02 -0800 (PST)
Kurt Vermeiren  wrote:

> I would agree with Matthew on this. I understand the rationale to not
> show the files because of the possible very big directories... but
> the documentation clearly states "directories and files"

I don't.  Not quite; here's my line of reasoning.

Let's cite the doc again:

| ·   no - Show no untracked files. 
| ·   normal - Shows untracked files and directories. 
| ·   all - Also shows individual files in untracked 
|   directories. 

While the formulation of the "normal" mode considered alone is indeed
open to interpretation ("what does «and directories» *really* stand
for?"), with the "all" mode thrown in, the picture is clear: if the
"all" mode «Also shows individual files in untracked directories» then
the other modes don't.

On the other hand, that's my interpretation.
If two other folks pereceive the doc the other way and get confused
this well might indicate the problem with the doc.
I'd suggest posting a dried out summary of our discussion on the main
Git list [1] and suggest a documentation update.

1. https://gist.github.com/tfnico/4441562

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[Konstantin Khomoutov]

On Sat, 28 Nov 2015 06:48:35 -0800 (PST)
justrajdeep  wrote:

> I want to push my entire local repo(present only with me) to a shared
> git repo as a branch in that.
> 
> I can do something like 
> 
> git remote add local-remote $PATH_TO_REPO_LOCATION
> git push local-remote -u master:$TREE_BRANCH
> 
> But this pushes only the master. Any way to push the whole thing with
> all its branches and everything?

How about

  git push local-remote 'refs/*:refs/*'

?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[rajdeep mondal]

Hi

I tried something like

git push local-remote -u 'refs/*:refs/$TREE_BRANCH/*'

it did not work as expected.



On Mon, Nov 30, 2015 at 9:21 PM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:

> On Sat, 28 Nov 2015 06:48:35 -0800 (PST)
> justrajdeep  wrote:
>
> > I want to push my entire local repo(present only with me) to a shared
> > git repo as a branch in that.
> >
> > I can do something like
> >
> > git remote add local-remote $PATH_TO_REPO_LOCATION
> > git push local-remote -u master:$TREE_BRANCH
> >
> > But this pushes only the master. Any way to push the whole thing with
> > all its branches and everything?
>
> How about
>
>   git push local-remote 'refs/*:refs/*'
>
> ?
>



-- 
==
Rajdeep

Nvidia Graphics Pvt Ltd

C-1 Wing A  ' Jacaranda'

Manyata Embassy Business Park

Outer Ring Road

Bangalore -560045
India
==

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] Create a new repo from a branch in another repo

[Anthony Hunter]

I'm new to git and looking into its usage and am responsible for the teams 
that will be using the repos.

As development goes on within a repo and time passes, the repo will start 
to get large just do to the number of commits. Is there a way that for 
example, as a release completes, I could branch off into a new repo to 
develop the next version? This will help keep the repos small and release 
specific. 

I'm aware of doing a shallow clone or even a branch clone, but I will still 
end up with users cloning the who thing by accident.

Any suggestions?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[rajdeep mondal]

Hi

1. i have repos:
  A with branches A1, A2, A3
  B with branches B1, B2, B3 etc

2. i want to push these 2 independent repo to a central repo MY_REPO

as branch A and branch B


3. The A1, A2, A3 are subbranches of branch A

4. B1, B2. B3 are subbranches of the branch B

- rajdeep



On Mon, Nov 30, 2015 at 9:48 PM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:

> On Mon, 30 Nov 2015 21:23:24 +0530
> rajdeep mondal  wrote:
>
> > I tried something like
> >
> > git push local-remote -u 'refs/*:refs/$TREE_BRANCH/*'
> >
> > it did not work as expected.
>
> I wonder what was expected then.
> To me, your invocation looks strange at best.
>
> Can you try to explain what you want to achieve in simple words?
>
> I mean, something like "
> 1) I have a repo with branches A, B and C.
> 2) I want to craft a command which would make branches A, B and C
>end up ... in the remote repo I intend to push them to.
> "
>
> Fill free to replace "..." in my description with something sensible.
> So far, I fail to clearly understand your intent.
>



-- 
==
Rajdeep

Nvidia Graphics Pvt Ltd

C-1 Wing A  ' Jacaranda'

Manyata Embassy Business Park

Outer Ring Road

Bangalore -560045
India
==

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Re: Where to start coding?

[Konstantin Khomoutov]

On Mon, 30 Nov 2015 09:06:29 -0800 (PST)
amey jain  wrote:

> Thanks that you wrote here. Yes that's right that I am new to all of
> it. Actually I want to go to GSoC and for that I started contributing
> to Open source. I am already running Ubuntu and subscribed to the
> mailing list of git to. I will for sure find some easy projects to
> tackle. But it was hard to find easy ones. Though I practice
> programming on C very much. I don't have any experience on finding
> projects. I think from now I will start from mailing lists and bug
> reporting in software.

Speaking as a Debian user, I'm able to point at [3] being a good
summary on how to start contributing to your OS.
I'm pretty sure Ubuntu has something like this as well.
At least folks at [4] should point to a right direction. ;-)

P.S.
Forgot to mention one thing in my original mail: no, Git does not have
any documentation outside of the specs of various on-disk data format
it maintains (which is present in the source tree in the form of .txt
files).  The only other source of documentation is comments.
Commit messages are a good source of documentation, too.
Don't forget that you can `git blame` a source code file of interest
and then study commit messages of those commits which touch the places
of that file which are of particular interest to you.

3. https://www.debian.org/intro/help
4. https://askubunu.com

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[Konstantin Khomoutov]

On Mon, 30 Nov 2015 23:15:32 +0530
rajdeep mondal  wrote:

> 1. i have repos:
>   A with branches A1, A2, A3
>   B with branches B1, B2, B3 etc
> 
> 2. i want to push these 2 independent repo to a central repo MY_REPO
> 
> as branch A and branch B
> 
> 
> 3. The A1, A2, A3 are subbranches of branch A
> 
> 4. B1, B2. B3 are subbranches of the branch B

OK, that's clearer now.

The problem is that branches in Git do not form any sort of hierarchy
-- except for being related through the parts of history they may share.

Well, may be you just meant naming?
Like in `push origin A1 A/A1 B1 B/B1` ?
If yes, then:

1) In repo A, do:

   git push central 'refs/heads/*:refs/heads/A/*'

2) In repo B, do:

   git push central 'refs/heads/*:refs/heads/B/*'

Note that it won't push other sorts of refs (tags, notes, whatever else
you might have).  Pushing those would require a similar approach.

If that's what you really wanted, it worth repeating that when you push
A1 to A/A1, the remote A1 is not "a subbranch of A", it's a branch
named "A/A1".  If you'd push to A\A1 or A%A1 or any other similar
"strange" name, the result would be the same: a branch with a funky
name.  IOW, the fact some parts of Git use "/" for some sort of
"namespacing" of refs is just a convention.  People are free to use it,
too, just keep in mind this thing is simpler than it appears.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[rajdeep mondal]

Thanks. I will try it out.

On Tue, Dec 1, 2015 at 1:08 AM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:

> On Mon, 30 Nov 2015 23:15:32 +0530
> rajdeep mondal  wrote:
>
> > 1. i have repos:
> >   A with branches A1, A2, A3
> >   B with branches B1, B2, B3 etc
> >
> > 2. i want to push these 2 independent repo to a central repo MY_REPO
> >
> > as branch A and branch B
> >
> >
> > 3. The A1, A2, A3 are subbranches of branch A
> >
> > 4. B1, B2. B3 are subbranches of the branch B
>
> OK, that's clearer now.
>
> The problem is that branches in Git do not form any sort of hierarchy
> -- except for being related through the parts of history they may share.
>
> Well, may be you just meant naming?
> Like in `push origin A1 A/A1 B1 B/B1` ?
> If yes, then:
>
> 1) In repo A, do:
>
>git push central 'refs/heads/*:refs/heads/A/*'
>
> 2) In repo B, do:
>
>git push central 'refs/heads/*:refs/heads/B/*'
>
> Note that it won't push other sorts of refs (tags, notes, whatever else
> you might have).  Pushing those would require a similar approach.
>
> If that's what you really wanted, it worth repeating that when you push
> A1 to A/A1, the remote A1 is not "a subbranch of A", it's a branch
> named "A/A1".  If you'd push to A\A1 or A%A1 or any other similar
> "strange" name, the result would be the same: a branch with a funky
> name.  IOW, the fact some parts of Git use "/" for some sort of
> "namespacing" of refs is just a convention.  People are free to use it,
> too, just keep in mind this thing is simpler than it appears.
>



-- 
==
Rajdeep

Nvidia Graphics Pvt Ltd

C-1 Wing A  ' Jacaranda'

Manyata Embassy Business Park

Outer Ring Road

Bangalore -560045
India
==

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] how to push indepedent repos to individual branches in remote in git?

[Magnus Therning]

On Sat, Nov 28, 2015 at 06:48:35AM -0800, justrajdeep wrote:
> Hi
> 
> I want to push my entire local repo(present only with me) to a
> shared git repo as a branch in that.
> 
> I can do something like 
> 
> git remote add local-remote $PATH_TO_REPO_LOCATION
> git push local-remote -u master:$TREE_BRANCH
> 
> But this pushes only the master. Any way to push the whole thing
> with all its branches and everything?

What about `git push --all`?

/M

-- 
Magnus Therning  OpenPGP: 0xAB4DFBA4 
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe   http://therning.org/magnus

Of course I laugh at my own jokes. You can't trust strangers.
 -- Phyllis Diller

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature