[git-users] Re: Git workflow for Multiple SKU
I think it would be good if you maintain it separately as it would be easier to keep track. You could of course do the same if you keep it together. But I personally believe using git diff would become much easier. And also remember that each commit should only represent 1 logical change. Now suppose you did changed one file in one part, then it should be commit. Then you might change another file in another part. And thus when you do git log, you will have to see which file belongs to which part and then it would become tedious and unnecessary. And I don't see any harm in maintaining separate projects. On Friday, 21 August 2015 13:05:04 UTC+5:30, Irakli Lomidze wrote: > > Dear Sirs. > > I have Multiple SKU of my application, (eg Standard, Enterprise, Corporate) > > What is best or suggested git workflow for it. ? > or I should manage it in separate folders as separate project with > individual git standard flow ? > > > Thank you in Advance. > -- 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] Digest for git-users@googlegroups.com - 1 update in 1 topic
I think it would be good if you maintain it separately as it would be easier to keep track. You could of course do the same if you keep it together. But I personally believe using git diff would become much easier. And also remember that each commit should only represent 1 logical change. Now suppose you did changed one file in one part, then it should be commit. Then you might change another file in another part. And thus when you do git log, you will have to see which file belongs to which part and then it would become tedious and unnecessary. And I don't see any harm in maintaining separate projects. On 8/22/15, git-users@googlegroups.com wrote: > = > Today's topic summary > = > > Group: git-users@googlegroups.com > Url: > > https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/git-users/topics > > > - Git workflow for Multiple SKU [1 Update] > http://groups.google.com/group/git-users/t/b9565ea2d39cf30c > > > = > Topic: Git workflow for Multiple SKU > Url: http://groups.google.com/group/git-users/t/b9565ea2d39cf30c > = > > -- 1 of 1 -- > From: Irakli Lomidze > Date: Aug 21 12:35AM -0700 > Url: http://groups.google.com/group/git-users/msg/5b7d1166ef7a9 > > Dear Sirs. > > I have Multiple SKU of my application, (eg Standard, Enterprise, Corporate) > > What is best or suggested git workflow for it. ? > or I should manage it in separate folders as separate project with > individual git standard flow ? > > > Thank you in Advance. > > > > > > > -- > You received this digest because you're subscribed to updates for this > group. You can change your settings on the group membership page: > > https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/git-users/join > . > To unsubscribe from this group and stop receiving emails from it send an > email to git-users+unsubscr...@googlegroups.com. > > -- -Pranit Bauva -- 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] Why git doesn't track file's "read"/"write" permission?
On Thu, Aug 27, 2015 at 12:40 PM, Enzo Chi wrote: > I think git track executable permission, right? > > If so, files in git is "read only" and "not deployment too", why it track > "x" permission? > x permissions alter the functionality of the file. For example, if you have a build system that needs scripts to build and those scripts need to be x, then the x better be stored or the scripts are useless. > > Keep "read only" permission is useful in some scenario. And most important > thing is there's on harm to keep it (I am not a software developer, correct > me if I am wrong)? > That does not achieve anything from a safety perspective. If you lose/alter a file then you just checkout the version in HEAD again. Getting r/w permissions right would be hell anyway. Consider this: Start with a readonly file. Now I need to change it, so I make is locally writable and change it. Then I do a commit and push it again. Oops! I forgot to make it read only again before I pushed it, so now it is writable in the repo too. Better to just dodge this hangover by not having r/w. > > > > On Thursday, August 27, 2015 at 6:55:55 AM UTC+10, Philip Oakley wrote: >> >> >> I have post an question at >> http://superuser.com/questions/962861/how-to-use-git-to-commit-read-only-file >> >> >> I just want to know why GIT doesn't track read/write permission? >> >> What I want is just GIT keep what every I checked in? ( I am OK with the >> executable permission control) >> >> >> It's sort of a philosophical issue. If you are placing a file into a >> repository, it is by definition "read only". You can never 'write' the same >> revision, but with a different content - it would be a contradiction. Hence >> the r/w flags are ignored. >> >> It's important to remember that as concieved, Git is not a deployment >> tool, so it didn't need r/w permissions, and as open source DVCS, >> everything checked out would be local so the user would have full control, >> so read-only couldn't be relied on anyway, and we hope the user will >> contribute a change/improvement so 'write' it is! >> >> Likewise it doesn't store timestamps (of the files) either.. >> >> There is a Linus 'rant' somewhere on the issue.. >> >> Philip >> > -- > 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. > -- 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] Why git doesn't track file's "read"/"write" permission?
I think git track executable permission, right? If so, files in git is "read only" and "not deployment too", why it track "x" permission? Keep "read only" permission is useful in some scenario. And most important thing is there's on harm to keep it (I am not a software developer, correct me if I am wrong)? On Thursday, August 27, 2015 at 6:55:55 AM UTC+10, Philip Oakley wrote: > > > I have post an question at > http://superuser.com/questions/962861/how-to-use-git-to-commit-read-only-file > > > > I just want to know why GIT doesn't track read/write permission? > > What I want is just GIT keep what every I checked in? ( I am OK with the > executable permission control) > > > It's sort of a philosophical issue. If you are placing a file into a > repository, it is by definition "read only". You can never 'write' the same > revision, but with a different content - it would be a contradiction. Hence > the r/w flags are ignored. > > It's important to remember that as concieved, Git is not a deployment > tool, so it didn't need r/w permissions, and as open source DVCS, > everything checked out would be local so the user would have full control, > so read-only couldn't be relied on anyway, and we hope the user will > contribute a change/improvement so 'write' it is! > > Likewise it doesn't store timestamps (of the files) either.. > > There is a Linus 'rant' somewhere on the issue.. > > Philip > -- 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] Why git doesn't track file's "read"/"write" permission?
I have post an question at http://superuser.com/questions/962861/how-to-use-git-to-commit-read-only-file I just want to know why GIT doesn't track read/write permission? What I want is just GIT keep what every I checked in? ( I am OK with the executable permission control) It's sort of a philosophical issue. If you are placing a file into a repository, it is by definition "read only". You can never 'write' the same revision, but with a different content - it would be a contradiction. Hence the r/w flags are ignored. It's important to remember that as concieved, Git is not a deployment tool, so it didn't need r/w permissions, and as open source DVCS, everything checked out would be local so the user would have full control, so read-only couldn't be relied on anyway, and we hope the user will contribute a change/improvement so 'write' it is! Likewise it doesn't store timestamps (of the files) either.. There is a Linus 'rant' somewhere on the issue.. Philip -- 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] What does +refs/heads/*:refs/remotes/origin/* mean ?
# mpc8...@gmail.com / 2015-08-18 09:11:13 -0700: > what does +refs/heads/*:refs/remotes/origin/* mean ? see "CONFIGURED REMOTE-TRACKING BRANCHES" in git-fetch(1). -- roman -- 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] Why git doesn't track file's "read"/"write" permission?
I have post an question at http://superuser.com/questions/962861/how-to-use-git-to-commit-read-only-file I just want to know why GIT doesn't track read/write permission? What I want is just GIT keep what every I checked in? ( I am OK with the executable permission control) -- 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.
