Re: [git-users] creating a new branch

2015-07-20 Thread Nelson Efrain A. Cruz
what I was trying to say is: your repo contains the files inside administrator folder, so you can make a new folder called administrator inside your repo and move all the files in the repo inside that folder. Then the folder that contains your repo can be renamed to appointments and moved one

Re: [git-users] creating a new branch

2015-07-20 Thread Philip Oakley
: Monday, July 20, 2015 4:39 PM Subject: Re: [git-users] creating a new branch Why move the repo one folder up... It is already there...at C:\Apache24\htdocs\Appointments\Administrator\ I do not quite understand...but more importantly...changing the dir structure of my web project

Re: [git-users] creating a new branch

2015-07-20 Thread Nelson Efrain A. Cruz
Assuming that those are the only folders (and files), one solution could be: move all your files (git mv) inside a folder called Administrator (like C:\Apache24\htdocs\ Appointments\Administrator\Administrator) and then move the repo one folder up. I think this will be the easiest solution, of

Re: [git-users] creating a new branch

2015-07-20 Thread Dimitris Papageorgiou
Why move the repo one folder up... It is already there...at C:\Apache24\htdocs\Appointments\Administrator\ I do not quite understand...but more importantly...*changing the dir structure of my web project it is something I want to avoid..*.. Τη Δευτέρα, 20 Ιουλίου 2015 - 6:17:52 μ.μ. UTC+3, ο

Re: [git-users] Creating a new branch

2014-04-22 Thread Gergely Polonkai
Another common practise for release naming is the usage of tags. In my projects, for example, I have several tags like v1.0.0, v2.4.2 and such. On 21 Apr 2014 14:53, Simon Joseph Aquilina saquilina...@gmail.com wrote: Hi Konstantin, Thanks for your reply. Reading your reply make me think that

Re: [git-users] Creating a new branch

2014-04-22 Thread Nelson Efrain A. Cruz
Take a look (if you did not yet) at this two articles: 1- http://scottchacon.com/2011/08/31/github-flow.html 2- http://nvie.com/posts/a-successful-git-branching-model/ 2014-04-22 3:20 GMT-03:00 Gergely Polonkai gerg...@polonkai.eu: Another common practise for release naming is the usage of

Re: [git-users] Creating a new branch

2014-04-22 Thread Magnus Therning
On Mon, Apr 21, 2014 at 4:35 PM, Konstantin Khomoutov flatw...@users.sourceforge.net wrote: On Mon, 21 Apr 2014 05:53:41 -0700 (PDT) Simon Joseph Aquilina saquilina...@gmail.com wrote: Thanks for your reply. Reading your reply make me think that it is common practice to delete branches after

Re: [git-users] Creating a new branch

2014-04-21 Thread Konstantin Khomoutov
On Mon, 21 Apr 2014 02:55:50 -0700 (PDT) Simon Joseph Aquilina saquilina...@gmail.com wrote: I am new to git and I would like to know what are the best practices when creating a new branch. For example. If I get a request to do update website title from XYZ to ABC; then should I create a

Re: [git-users] Creating a new branch

2014-04-21 Thread Simon Joseph Aquilina
Hi Konstantin, Thanks for your reply. Reading your reply make me think that it is common practice to delete branches after development on these has finished (for example branches used only to solve a bug or add a feature). Is this so. I was planning to also have branches for releases. For

Re: [git-users] Creating a new branch

2014-04-21 Thread Konstantin Khomoutov
On Mon, 21 Apr 2014 05:53:41 -0700 (PDT) Simon Joseph Aquilina saquilina...@gmail.com wrote: Thanks for your reply. Reading your reply make me think that it is common practice to delete branches after development on these has finished (for example branches used only to solve a bug or add a