[git-users] Re: Branching Questions
Thanksthat helped me understand this process a lot better. Truly appreciate it. You're right, the first response fixed the issue. I just wondered if there was a better way to get the branch to begin with, but I suppose since that way works it is the way I should do it. On Friday, February 27, 2015 at 12:00:47 PM UTC-8, Michael J. Mahony wrote: I am developing a web application and I am using GitHub to store my source code. I set up a repository and have a MASTER branch. I am fairly new to using Git and wanted to use this as a learning process. Because I am using this as a learning process for using Git, I have some questions. I got my MASTER branch to a point where it was stable and now I want to start doing some serious development. I had an up to date copy of MASTER on my machine. I used bash and issued this command to create a DEV branch: git checkout -b dev origin/master Now when I do: git branch -a I see this list: https://lh4.googleusercontent.com/-VBQZzyatwg4/VPCrRu25bVI/NGM/W0ExjjkVNmU/s1600/git-branches.PNG I have also pushed this dev branch. However, on GitHub it only shows one branch--MASTER How can I get the other branch to be on GitHub so that I can grab it from another machine when required? Can someone explain to me how to accomplish this so that I am able to have a branch for dev? Thanks! Mike -- 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] Git workflow with MySQL scripts
I am using MySQL on my local Windows laptop to compile data and produce reports for my enterprise related to PIV issuance. I have a folder named sqlScripts where I keep all of the script files. I am using Git and SourceTree to manage versioning of these scripts, but I am apparently not doing it quite right. I set up this sqlScript folder as as a local Git repository, and am making commits on a regular basis. The script files each perform a specific task, such as importing data sets ImportActiveDirectory.sql ImportPIVIssuanceData.sql ImportPIVFailureData.sql and producing detailed reports: PIVIssuanceReport.sql PIVUsageReport.sql etc... The challenge that I have is that although all of these scripts loosely relate to the PIV project, but pretty much stand on their own for each function. I would like to be able to use tags to monitor version numbers for each of the scripts ( 1.0, 1.1, 1.2, 2.0, and so on). In order to do this, do I need to create a separate repository for each script? If so, that would seem to be a lot of extra work. Can anyone suggest a workflow that will help me to monitor and track version numbers for each script separately? I have posted this same question on StackOverflow: http://stackoverflow.com/questions/28833957/git-workflow-with-mysql-scripts -- 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] Newbie in Git
On Tue, 3 Mar 2015 06:50:45 -0800 (PST) Prudhvee Narasimha Sadha prudhvi.s...@gmail.com wrote: What is your intent when you call git -C '' cmd ? I mean, what this command is supposed to do? Please describe this as precise as possible. -- 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] Newbie in Git
Hi, I'm a newbie to git. I started working on git. I cloned the git repository and started hacking it. I need a suggestion on how to start working on the micro project Make git -C '' cmd not to barf. Thank you for your suggestion in advance. Regards, Prudhvee, open source enthusiast. -- 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] Git workflow with MySQL scripts
On Tue, 3 Mar 2015 07:17:31 -0800 (PST) Michael Sheaver mshea...@me.com wrote: I am using MySQL on my local Windows laptop to compile data and produce reports for my enterprise related to PIV issuance. [...] The challenge that I have is that although all of these scripts loosely relate to the PIV project, but pretty much stand on their own for each function. I would like to be able to use tags to monitor version numbers for each of the scripts ( 1.0, 1.1, 1.2, 2.0, and so on). In order to do this, do I need to create a separate repository for each script? If so, that would seem to be a lot of extra work. Can anyone suggest a workflow that will help me to monitor and track version numbers for each script separately? I would keep things as simple as possible and just do this: 1) Turn your folder into a Git repo (`git init .`). 2) Add all your scripts into it and record the first commit; mention current version of each script in the extended part of the commit message. When a new version of a particular script appears, update the appropriate file in your folder to match it, `git add` that script file solely and record a new commit. You will then be able to see the history of changes of a particular script file by using git log -- scriptFileName.sql There is no tags in my simplistic picture, but I'd just record version of the script file recorded in a commit using its version number in the commit message -- you will see them in the `git log` output and will be able to use git-log's search facilities to search for a particular version (present in the commit message). You can still use tags with this approach -- just devise proper namespacing for your tag -- for instance, put the base name of a script file (without the extension) into tags related to that script file, and then tag each commit recording a new version of that file with such a tag -- say, if you've just recorded version 3.2 of mumboJumbo.sql, tag it using mumboJumbo-v3.5. If you feel extravagant, you can even not use branches at all, just shovel new versions of your script files into the repo using the standard if lesser known git hash-object -w myScript.sql and then tag whatever SHA-1 hash it printed out using the naming scheme outlined above. You will then only have tagged blobs and no history at all (it will be implicitly encoded in the tag names). I'd still prefer a single branch and may be tags on its commits. I have posted this same question on StackOverflow: http://stackoverflow.com/questions/28833957/git-workflow-with-mysql-scripts Thanks for mentioning -- this level of netiquette is rare these days ;-) -- 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] Git workflow with MySQL scripts
Konstantin, Many thanks for your assistance here! Like you, I prefer to keep things simple and not use branches for single-file scenarios like these scripts. I usually use the extended comments section of the commit comment to include a brief synopsis of the changes in the commit. I wonder if using your filename-version number suggestion in the title section might work? On Tuesday, March 3, 2015 at 11:52:04 AM UTC-5, Konstantin Khomoutov wrote: On Tue, 3 Mar 2015 07:17:31 -0800 (PST) Michael Sheaver mshe...@me.com javascript: wrote: I am using MySQL on my local Windows laptop to compile data and produce reports for my enterprise related to PIV issuance. [...] The challenge that I have is that although all of these scripts loosely relate to the PIV project, but pretty much stand on their own for each function. I would like to be able to use tags to monitor version numbers for each of the scripts ( 1.0, 1.1, 1.2, 2.0, and so on). In order to do this, do I need to create a separate repository for each script? If so, that would seem to be a lot of extra work. Can anyone suggest a workflow that will help me to monitor and track version numbers for each script separately? I would keep things as simple as possible and just do this: 1) Turn your folder into a Git repo (`git init .`). 2) Add all your scripts into it and record the first commit; mention current version of each script in the extended part of the commit message. When a new version of a particular script appears, update the appropriate file in your folder to match it, `git add` that script file solely and record a new commit. You will then be able to see the history of changes of a particular script file by using git log -- scriptFileName.sql There is no tags in my simplistic picture, but I'd just record version of the script file recorded in a commit using its version number in the commit message -- you will see them in the `git log` output and will be able to use git-log's search facilities to search for a particular version (present in the commit message). You can still use tags with this approach -- just devise proper namespacing for your tag -- for instance, put the base name of a script file (without the extension) into tags related to that script file, and then tag each commit recording a new version of that file with such a tag -- say, if you've just recorded version 3.2 of mumboJumbo.sql, tag it using mumboJumbo-v3.5. If you feel extravagant, you can even not use branches at all, just shovel new versions of your script files into the repo using the standard if lesser known git hash-object -w myScript.sql and then tag whatever SHA-1 hash it printed out using the naming scheme outlined above. You will then only have tagged blobs and no history at all (it will be implicitly encoded in the tag names). I'd still prefer a single branch and may be tags on its commits. I have posted this same question on StackOverflow: http://stackoverflow.com/questions/28833957/git-workflow-with-mysql-scripts Thanks for mentioning -- this level of netiquette is rare these days ;-) -- 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.
