then knows about the
branch. Is there some sort of logic to this? I don't get git because it
defies any kind of understanding I try to apply to it.
Your help is greatly appreciated.
Blake McBride
--
You received this message because you are subscribed to the Google Groups Git
for human beings
. No repository changes occurred in between.
If what it is showing is correct, I am totally lost. I am clearly missing
some basic idea here.
Thanks.
Once you check out versionx it will become a local branch.
On Sat, Oct 19, 2013 at 1:51 PM, Blake McBride blak...@gmail.comjavascript
created remotely are kept
noted as such (even though I have a local copy). When I check the branch
out, it becomes a totally new local branch.
Thanks for the help!
Blake
On Friday, October 18, 2013 9:47:10 PM UTC-5, Felipe Contreras wrote:
On Fri, Oct 18, 2013 at 9:31 PM, Blake McBride
blak
hour
build. I am sure this must be a common problem.
Stated another way - when you have a very large project, branching becomes
a significant problem because of build times. Are there common solutions
to this sort of problem?
Thanks.
Blake McBride
--
You received this message because you
problems.
Thanks.
Blake McBride
On Saturday, October 19, 2013 5:52:00 PM UTC-5, Gergely Polonkai wrote:
Hello,
according to your description, your project seems to be something like the
Linux kernel, and Git handles that just fine. Depending on your build
environment, Git branches may help you
, and solve the problem/merge your code into the master.
The problem lies in switching between branches that already exist, which
might force a clean build...
As a side note, I'm really enjoying Go's ridiculously fast build times.
Wes
On Sun, Oct 20, 2013 at 3:59 AM, Blake McBride blak
long lived branches be in separate checked out
folders?
On Sun, Oct 20, 2013 at 6:39 AM, Blake McBride blak...@gmail.comjavascript:
wrote:
Yes, of course, creating a totally new branch from where you are doesn't
cause any problems because nothing changes.
The problem is that, I
See inline comments below:
On Sunday, October 20, 2013 12:34:32 PM UTC-5, Magnus Therning wrote:
On Sun, Oct 20, 2013 at 12:59:21AM -0700, Blake McBride wrote:
Not sure what you mean about designed well, but in order to switch
branches without having to do a full rebuild would involve
On Sunday, October 20, 2013 12:59:55 PM UTC-5, Konstantin Khomoutov wrote:
On Sun, 20 Oct 2013 19:34:32 +0200
Magnus Therning mag...@therning.org javascript: wrote:
[...]
Well, many of the issues you mention can be solved by using a build
system that can take advantage of a shared
.
Thanks.
Blake
On Monday, October 21, 2013 9:38:59 AM UTC-5, Dale Worley wrote:
From: Blake McBride blak...@gmail.com javascript:
Not sure what you mean about designed well, but in order to switch
branches
without having to do a full rebuild would involve:
[lots of stuff]
I
-branches/
- Original Message -
*From:* Blake McBride javascript:
*To:* git-...@googlegroups.com javascript:
*Sent:* Monday, October 21, 2013 4:03 PM
*Subject:* Re: [git-users] GIT with large projects
I am sure this can be done. The problem is:
1. It would be a complex setup and may
11 matches
Mail list logo
