Docs: Does ticgit-ng have a ticgit-ng branch?

[holtzermann17]

It seems not? Can someone adjust the documentation appropriately?

[jeffWelling]

TicGit-ng should use the 'ticgit' branch if it exists, or it will create and use the 'ticgit-ng' branch. This was done for backwards compatibility between TicGit-ng and TicGit.

I will update the documentation to clarify that, thank you for pointing out the ambiguity. I'll leave the bug open until the corresponding documentation is updated.
Cheers!

[holtzermann17]

I'm also wondering whether the development version of TicGit-ng has a ticgit branch for purposes of keeping track of it's own issues. After checking out the code, I don't see one...

$ git branch -a
* deving
  remotes/origin/2010.09.03
  remotes/origin/HEAD -> origin/deving
  remotes/origin/deving
  remotes/origin/edit_comments
  remotes/origin/edit_title
  remotes/origin/fixing_stuff
  remotes/origin/hotfix-1.0.2.14
  remotes/origin/master
  remotes/origin/merge_paulboone
  remotes/origin/relicense_as_gpl
  remotes/origin/rename_ticgit-ng
  remotes/origin/switch_to_grit
  remotes/origin/switch_to_rugged
  remotes/origin/sync_with_other_repos
  remotes/origin/verbose_puts

[jeffWelling]

I occasionally will keep a couple notes or todo items in a ticgit-ng branch on my local development machine, but due to the fact that TicGit-ng can not yet synchronize with other bug trackers, I would be the only one who easily file bugs that way. So to accomodate other people easily filing bugs against TicGit-ng I've just been using Github Issues as the 'official' bug tracker for now.

Once synchronization works, I will be able to respond to issues filed on Github Issues by commenting on the ticgit-ng branch on my own machine, allowing me to use TicGit-ng to track bugs in itself while also allowing people to easily file bugs via Github Issues or other bug trackers,