You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(30) |
Aug
(79) |
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
From: SourceForge.net <no...@so...> - 2008-08-03 21:35:07
|
Bugs item #2033121, was opened at 2008-07-30 16:34 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033121&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: v0.1.0 (fixed in) Status: Closed >Resolution: Fixed Priority: 2 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Nobody/Anonymous (nobody) Summary: GitMv Javadocs need correcting Initial Comment: The javadocs state there is an "options" argument where there is none (copy and paste error), see below. Also, the File arguments claim to need a "non-zero length argument", that sounds like strings not File objects. public GitMvResponse mv(java.io.File repositoryPath, java.io.File source, java.io.File destination) throws java.io.IOException, JavaGitException Moves the specified source file/symlink/directory to the destination file/symlink/directory. If destination is non-existant then same as rename. Parameters: repositoryPath - The path to the repository, to be treated as root folder for git-mv operation. A non-zero length argument is required for this parameter, otherwise a NullPointerException or IllegalArgumentException will be thrown. options - The options to git-mv command. source - The source file/folder/symlink which is to be renamed or moved to a different location. A non-zero length argument is required for this parameter, otherwise a NullPointerException or IllegalArgumentException will be thrown. destination - The destination file/folder/symlink which the source is renamed or moved to. A non-zero length argument is required for this parameter, otherwise a NullPointerException or IllegalArgumentException will be thrown. ---------------------------------------------------------------------- Comment By: Andrew Case (andrewcase) Date: 2008-07-30 18:20 Message: Logged In: YES user_id=2143267 Originator: YES Latest build corrected this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033121&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:34:18
|
Bugs item #2033470, was opened at 2008-07-31 00:31 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) Status: Closed Resolution: Fixed Priority: 6 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Iterator/Iterable inconsistencies Initial Comment: GitStatusResponse has methods to get iterators over lists of Files. Most have been updated to return Iterable's but some are still returning Iterator's GitStatusResponse().getNewFilesToCommitIterarator() for example returns and Iterator. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 16:42 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 15:59 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:42 Message: Logged In: YES user_id=1099750 Originator: NO Confirming fixed. Marking closed. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 03:54 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:49 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:33:36
|
Bugs item #2033200, was opened at 2008-07-30 18:18 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033200&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: nutans (nutans) Summary: GitMvResponse doesn't let us know about success Initial Comment: GitMvResponse() doesn't seem to let us know if the operation was a success/failure. ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-02 16:33 Message: Logged In: YES user_id=2152864 Originator: NO This is fixed and still open for 2-3 days. Is verified by James. So, I am closing it. ~Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-07-30 21:38 Message: Logged In: YES user_id=1099750 Originator: NO Andrew, it is expected that GitMv does not notify when a move was successful. This follows the response that git-mv itself gives. Nutan, if the JavaDocs for GitMv/GitMvResponse do not already say so, please update them to say that no response is expected when git-mv successfully moves the file. Cheers, James ---------------------------------------------------------------------- Comment By: Andrew Case (andrewcase) Date: 2008-07-30 21:35 Message: Logged In: YES user_id=2143267 Originator: YES I'm fine with that as a the implementation. But then you need to put it in the javadocs that if it passes back a valid GitMvResponse as opposed to throwing an exception, then it is guaranteed to have succeeded. Otherwise as far as I know it good have failed. ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-07-30 19:32 Message: Logged In: YES user_id=2152864 Originator: NO I made it behave as git-mv command does. On successful move/rename it doesn't give any message(when there is none received from the git-mv execution), but, if the move/rename fails for any reason, proper exception messages are generated and thrown. Do you think there should be some difference in behavior? Should there be a response message even if there is no message coming from git-mv command? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033200&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:33:27
|
Bugs item #2024082, was opened at 2008-07-21 20:40 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2024082&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: CLI Implementation >Group: v0.1.0 (fixed in) Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Michelle Osborne (mso206) Assigned to: Nobody/Anonymous (nobody) Summary: Git status incorrectly reporting modifications as staged Initial Comment: Running git status seems to report all modified files as 'modified to commit' files even when they are not staged. Here is the actual git status that I get on the command line: # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # modified: src/Modified.java # deleted: src/Removed.java # deleted: src/RemovedNotStaged.java # # Changed but not updated: # (use "git add <file>..." to update what will be committed) # # modified: src/ModifiedNotStaged.java # # Untracked files: # (use "git add <file>..." to include in what will be committed) # # .classpath # .project # bin/ The result of calling statusAll is that both Modified.java and ModifiedNotStaged.java are 'modified to commit', rather than Modified.java being 'modified to commit' and ModifiedNotStaged.java being 'modified not updated'. ---------------------------------------------------------------------- Comment By: Michelle Osborne (mso206) Date: 2008-07-22 19:47 Message: Logged In: YES user_id=2154647 Originator: YES My mistake - this is not a bug, I should have been calling 'status' rather than 'statusAll'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2024082&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:32:42
|
Bugs item #2036823, was opened at 2008-08-03 10:47 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 8 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: Change *Iterator to *Iterable methods in GitStatusResponse Initial Comment: GitStatusResponse has a few methods that return Iterable objects. They should have their names updated to be consistently named and to reflect the fact that they no longer return Iterators. Their JavaDocs also need to be updated to reflect the fact that they return Iterable. The methods are: getNewFilesToCommitIterarator() getDeletedFilesToCommitIterator() getModifiedFilesToCommitIterator() getDeletedFilesNotUpdatedIterator() getModifiedFilesNotUpdatedIterator() getRenamedFilesToCommitIterator() getUntrackedFiles() ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 15:59 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 15:44 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 13:55 Message: Logged In: YES user_id=1099750 Originator: YES Looks good. Closing and marking fixed in 0.1.0. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:50 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:49 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:30:23
|
Bugs item #2033959, was opened at 2008-07-31 10:42 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033959&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 9 Private: No Submitted By: Paul M Bethe (pbethe) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: finish converting GitStatusResponse to iteratable Initial Comment: Michelle made the request to change the various 'getModifiedFilesToCommitIterator' etc. to return Iterable<File> instead of Iterator<File> however only *most* of the functions were changed, but not all. So common code on the gitclipse side to run through the various results is now broken. still to convert:: getNewFilesToCommitIterarator ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-02 13:06 Message: Logged In: YES user_id=2143686 Originator: NO Updated getNewFilesToCommitIterarator() method. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033959&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:29:27
|
Bugs item #2033470, was opened at 2008-07-31 00:31 Message generated for change (Settings changed) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: None >Status: Closed Resolution: Fixed Priority: 6 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Iterator/Iterable inconsistencies Initial Comment: GitStatusResponse has methods to get iterators over lists of Files. Most have been updated to return Iterable's but some are still returning Iterator's GitStatusResponse().getNewFilesToCommitIterarator() for example returns and Iterator. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 16:42 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 15:59 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:42 Message: Logged In: YES user_id=1099750 Originator: NO Confirming fixed. Marking closed. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 03:54 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:49 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:26:55
|
Bugs item #2029073, was opened at 2008-07-26 21:22 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2029073&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: Make GitAddOptions optional Initial Comment: I'm wondering if api commands can have optional 'options' when they really are optional. I see it done both ways (git-mv vs. git-add). I would think that if the command line options are options, so should the object paramaters: Can GitAdd provide: public GitAddResponse add(java.io.File repositoryPath, java.io.File file) throws java.io.IOException, JavaGitException as well as public GitAddResponse add(java.io.File repositoryPath, GitAddOptions options, java.io.File file) throws java.io.IOException, JavaGitException Thanks, -- Drew ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 17:26 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, I finished providing comments on this fix. Please comment in the bug once you have reviewed my comments and committed changes. Thanks, James ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 14:52 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, What revision did you commit these changes on? Thanks, James ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:46 Message: Logged In: YES user_id=2143686 Originator: NO Two additional APIs have been added to GitAdd with no options needed. - public GitAddResponse add(File repositoryPath, File file) throws JavaGitException, IOException; - public GitAddResponse add(File repositoryPath, List<File> filePaths) throws JavaGitException, IOException; ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:44 Message: Logged In: YES user_id=2143686 Originator: NO Two additional APIs have been added to GitAdd with no options needed. - public GitAddResponse add(File repositoryPath, File file) throws JavaGitException, IOException; - public GitAddResponse add(File repositoryPath, List<File> filePaths) throws JavaGitException, IOException; ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 01:08 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, Nutan, If one of you can fix this before the build, that would be great. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-07-31 10:37 Message: Logged In: YES user_id=2152864 Originator: NO Gurdeep, Have you done this already(on your machine)? Or, do you want me to assign it to myself and fix the problem? ~Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2029073&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 21:23:36
|
Bugs item #2027353, was opened at 2008-07-24 21:08 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2027353&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Michelle Osborne (mso206) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse missing renamed files Initial Comment: GitStatusResponse does not return any handle on files that were renamed. If possible it would be nice to know the name of the file both before and after the rename. ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 17:23 Message: Logged In: YES user_id=1099750 Originator: NO Marking as closed and fixed for v0.1.0. If the issue comes back up, open a new bug and reference this bug. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 01:07 Message: Logged In: YES user_id=1099750 Originator: NO Michelle, Gurdeep indicates this has been fixed. Does it work for you? James ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-02 16:57 Message: Logged In: YES user_id=2143686 Originator: NO Added the functionality to get renamed files from GitStatus. response,getRenamedFilesToCommitIterator() will return Iterable object over list of files that have been renamed. The files returned are the files after renaming. ---------------------------------------------------------------------- Comment By: Michelle Osborne (mso206) Date: 2008-07-24 21:22 Message: Logged In: YES user_id=2154647 Originator: YES Actually on second thought I think it's fine to just know the name of the file after rename. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2027353&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 19:59:04
|
Bugs item #2036823, was opened at 2008-08-03 10:47 Message generated for change (Comment added) made by dhindsg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: Fixed Priority: 8 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: Change *Iterator to *Iterable methods in GitStatusResponse Initial Comment: GitStatusResponse has a few methods that return Iterable objects. They should have their names updated to be consistently named and to reflect the fact that they no longer return Iterators. Their JavaDocs also need to be updated to reflect the fact that they return Iterable. The methods are: getNewFilesToCommitIterarator() getDeletedFilesToCommitIterator() getModifiedFilesToCommitIterator() getDeletedFilesNotUpdatedIterator() getModifiedFilesNotUpdatedIterator() getRenamedFilesToCommitIterator() getUntrackedFiles() ---------------------------------------------------------------------- >Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 15:59 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 15:44 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 13:55 Message: Logged In: YES user_id=1099750 Originator: YES Looks good. Closing and marking fixed in 0.1.0. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:50 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:49 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 19:17:50
|
Bugs item #2037045, was opened at 2008-08-03 15:17 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037045&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: None Priority: 4 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Nobody/Anonymous (nobody) Summary: Move basic method argument checks from IGit* to Git* Initial Comment: Right now, method argument checks are being done in either the Git* methods, the CLI implementations of the IGit* interfaces, or both. Since the end user should only ever use the classes under edu.nyu.cs.javagit.api, it makes sense to only make the basic argument checks in the ...api.commands.Git* methods and not in the implementations of the ...client.IGit* interfaces. Move all basic argument checks to the edu.nyu.cs.javagit.api.commands.Git* methods. ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 15:17 Message: Logged In: YES user_id=1099750 Originator: YES This bug can wait until after the 0.1.0 build. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037045&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 19:17:23
|
Bugs item #2037045, was opened at 2008-08-03 15:17 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037045&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: None Priority: 4 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Nobody/Anonymous (nobody) Summary: Move basic method argument checks from IGit* to Git* Initial Comment: Right now, method argument checks are being done in either the Git* methods, the CLI implementations of the IGit* interfaces, or both. Since the end user should only ever use the classes under edu.nyu.cs.javagit.api, it makes sense to only make the basic argument checks in the ...api.commands.Git* methods and not in the implementations of the ...client.IGit* interfaces. Move all basic argument checks to the edu.nyu.cs.javagit.api.commands.Git* methods. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2037045&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 18:52:59
|
Bugs item #2029073, was opened at 2008-07-26 21:22 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2029073&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Commands API >Group: New Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: Make GitAddOptions optional Initial Comment: I'm wondering if api commands can have optional 'options' when they really are optional. I see it done both ways (git-mv vs. git-add). I would think that if the command line options are options, so should the object paramaters: Can GitAdd provide: public GitAddResponse add(java.io.File repositoryPath, java.io.File file) throws java.io.IOException, JavaGitException as well as public GitAddResponse add(java.io.File repositoryPath, GitAddOptions options, java.io.File file) throws java.io.IOException, JavaGitException Thanks, -- Drew ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 14:52 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, What revision did you commit these changes on? Thanks, James ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:46 Message: Logged In: YES user_id=2143686 Originator: NO Two additional APIs have been added to GitAdd with no options needed. - public GitAddResponse add(File repositoryPath, File file) throws JavaGitException, IOException; - public GitAddResponse add(File repositoryPath, List<File> filePaths) throws JavaGitException, IOException; ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:44 Message: Logged In: YES user_id=2143686 Originator: NO Two additional APIs have been added to GitAdd with no options needed. - public GitAddResponse add(File repositoryPath, File file) throws JavaGitException, IOException; - public GitAddResponse add(File repositoryPath, List<File> filePaths) throws JavaGitException, IOException; ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 01:08 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, Nutan, If one of you can fix this before the build, that would be great. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-07-31 10:37 Message: Logged In: YES user_id=2152864 Originator: NO Gurdeep, Have you done this already(on your machine)? Or, do you want me to assign it to myself and fix the problem? ~Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2029073&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 18:33:47
|
Bugs item #2036301, was opened at 2008-08-02 21:06 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: New Status: Open Resolution: Fixed Priority: 7 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: nutans (nutans) Summary: Fix JavaDocs to print no warnings during javadoc generation Initial Comment: JavaDoc generation prints many warnings. Fix the code so those warnings are not generated. ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 14:33 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, The changes look good. I started a review for the changes and left a comment or two. Please take a look; review Javagit-14. Thanks, James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 11:26 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, I have fixed it. Please confirm and close it. Thanks, Nutan ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:51 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, You can see the warnings by running 'mvn javadoc:javadoc' against the JavaGit source code. The warnings start appearing near the bottom of the output (and there is a lot of output. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 10:47 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, What kind of warnings does it generate? Can you give me little info about it or let me know about how to generate javadocs and see it for myself. Thanks, Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 17:55:32
|
Bugs item #2036823, was opened at 2008-08-03 10:47 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 8 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: Change *Iterator to *Iterable methods in GitStatusResponse Initial Comment: GitStatusResponse has a few methods that return Iterable objects. They should have their names updated to be consistently named and to reflect the fact that they no longer return Iterators. Their JavaDocs also need to be updated to reflect the fact that they return Iterable. The methods are: getNewFilesToCommitIterarator() getDeletedFilesToCommitIterator() getModifiedFilesToCommitIterator() getDeletedFilesNotUpdatedIterator() getModifiedFilesNotUpdatedIterator() getRenamedFilesToCommitIterator() getUntrackedFiles() ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 13:55 Message: Logged In: YES user_id=1099750 Originator: YES Looks good. Closing and marking fixed in 0.1.0. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:50 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:49 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 16:50:18
|
Bugs item #2036823, was opened at 2008-08-03 10:47 Message generated for change (Comment added) made by dhindsg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: Fixed Priority: 8 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: Change *Iterator to *Iterable methods in GitStatusResponse Initial Comment: GitStatusResponse has a few methods that return Iterable objects. They should have their names updated to be consistently named and to reflect the fact that they no longer return Iterators. Their JavaDocs also need to be updated to reflect the fact that they return Iterable. The methods are: getNewFilesToCommitIterarator() getDeletedFilesToCommitIterator() getModifiedFilesToCommitIterator() getDeletedFilesNotUpdatedIterator() getModifiedFilesNotUpdatedIterator() getRenamedFilesToCommitIterator() getUntrackedFiles() ---------------------------------------------------------------------- >Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:50 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:49 Message: Logged In: YES user_id=2143686 Originator: NO Method names have been changed to - public Iterable<File> getNewFilesToCommit() public Iterable<File> getDeletedFilesToCommit() public Iterable<File> getModifiedFilesToCommit() public Iterable<File> getDeletedFilesNotUpdated() public Iterable<File> getModifiedFilesNotUpdated() public Iterable<File> getRenamedFilesToCommit() public Iterable<File> getUntrackedFiles() Mail is also sent to gitclipse-devel team. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 16:04:41
|
Bugs item #2031803, was opened at 2008-07-29 15:44 Message generated for change (Comment added) made by dhindsg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031803&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Fixed Priority: 9 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Returns Invalid Files Initial Comment: The GitStatusResponse.getUntracked() gives back a list of invalid files. When I have a project in: /home/acase/projects/runtime-EclipseApplication/hello With untracked files: .classpath .project bin It passes back the iterator with files: untracked: /home/acase/.classpath untracked: /home/acase/.project untracked: /home/acase/bin These aren't valid files. It should be: /home/acase/projects/runtime-EclipseApplication/hello/.classpath /home/acase/projects/runtime-EclipseApplication/hello/.project /home/acase/projects/runtime-EclipseApplication/hello/bin ---------------------------------------------------------------------- >Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 12:04 Message: Logged In: YES user_id=2143686 Originator: NO Changed the status to FIXED. ( Fixed By Max ) Hi Max, It's perfectly ok so no worries. ---------------------------------------------------------------------- Comment By: Maxim A. (ma1683) Date: 2008-08-03 11:06 Message: Logged In: YES user_id=2155661 Originator: NO I've modified the CliGitStatus.java to create files with absolute paths, ensuring proper behaviour. I've used CliGitCommit.java as a model. Please verify (svn cange #651). Gurdeep, if you were working on this, I apologize for stepping over your feet... ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 01:10 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, This seems like a pretty important bug to fix. What is its status? James ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031803&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 15:22:48
|
Bugs item #2036301, was opened at 2008-08-02 21:06 Message generated for change (Settings changed) made by nutans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: New Status: Open Resolution: None Priority: 7 Private: No Submitted By: James H. Linder (jhlinder) >Assigned to: nutans (nutans) Summary: Fix JavaDocs to print no warnings during javadoc generation Initial Comment: JavaDoc generation prints many warnings. Fix the code so those warnings are not generated. ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:51 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, You can see the warnings by running 'mvn javadoc:javadoc' against the JavaGit source code. The warnings start appearing near the bottom of the output (and there is a lot of output. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 10:47 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, What kind of warnings does it generate? Can you give me little info about it or let me know about how to generate javadocs and see it for myself. Thanks, Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 15:06:57
|
Bugs item #2031803, was opened at 2008-07-29 15:44 Message generated for change (Comment added) made by ma1683 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031803&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 9 Private: No Submitted By: Andrew Case (andrewcase) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Returns Invalid Files Initial Comment: The GitStatusResponse.getUntracked() gives back a list of invalid files. When I have a project in: /home/acase/projects/runtime-EclipseApplication/hello With untracked files: .classpath .project bin It passes back the iterator with files: untracked: /home/acase/.classpath untracked: /home/acase/.project untracked: /home/acase/bin These aren't valid files. It should be: /home/acase/projects/runtime-EclipseApplication/hello/.classpath /home/acase/projects/runtime-EclipseApplication/hello/.project /home/acase/projects/runtime-EclipseApplication/hello/bin ---------------------------------------------------------------------- >Comment By: Maxim A. (ma1683) Date: 2008-08-03 11:06 Message: Logged In: YES user_id=2155661 Originator: NO I've modified the CliGitStatus.java to create files with absolute paths, ensuring proper behaviour. I've used CliGitCommit.java as a model. Please verify (svn cange #651). Gurdeep, if you were working on this, I apologize for stepping over your feet... ---------------------------------------------------------------------- Comment By: James H. Linder (jhlinder) Date: 2008-08-03 01:10 Message: Logged In: YES user_id=1099750 Originator: NO Gurdeep, This seems like a pretty important bug to fix. What is its status? James ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2031803&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 14:51:21
|
Bugs item #2036301, was opened at 2008-08-02 21:06 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: New Status: Open Resolution: None Priority: 7 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Nobody/Anonymous (nobody) Summary: Fix JavaDocs to print no warnings during javadoc generation Initial Comment: JavaDoc generation prints many warnings. Fix the code so those warnings are not generated. ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:51 Message: Logged In: YES user_id=1099750 Originator: YES Hi Nutan, You can see the warnings by running 'mvn javadoc:javadoc' against the JavaGit source code. The warnings start appearing near the bottom of the output (and there is a lot of output. James ---------------------------------------------------------------------- Comment By: nutans (nutans) Date: 2008-08-03 10:47 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, What kind of warnings does it generate? Can you give me little info about it or let me know about how to generate javadocs and see it for myself. Thanks, Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 14:48:01
|
Bugs item #2036823, was opened at 2008-08-03 10:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: New Status: Open Resolution: None Priority: 8 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Nobody/Anonymous (nobody) Summary: Change *Iterator to *Iterable methods in GitStatusResponse Initial Comment: GitStatusResponse has a few methods that return Iterable objects. They should have their names updated to be consistently named and to reflect the fact that they no longer return Iterators. Their JavaDocs also need to be updated to reflect the fact that they return Iterable. The methods are: getNewFilesToCommitIterarator() getDeletedFilesToCommitIterator() getModifiedFilesToCommitIterator() getDeletedFilesNotUpdatedIterator() getModifiedFilesNotUpdatedIterator() getRenamedFilesToCommitIterator() getUntrackedFiles() ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036823&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 14:47:33
|
Bugs item #2036301, was opened at 2008-08-02 21:06 Message generated for change (Comment added) made by nutans You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: New Status: Open Resolution: None Priority: 7 Private: No Submitted By: James H. Linder (jhlinder) Assigned to: Nobody/Anonymous (nobody) Summary: Fix JavaDocs to print no warnings during javadoc generation Initial Comment: JavaDoc generation prints many warnings. Fix the code so those warnings are not generated. ---------------------------------------------------------------------- >Comment By: nutans (nutans) Date: 2008-08-03 10:47 Message: Logged In: YES user_id=2152864 Originator: NO Hi James, What kind of warnings does it generate? Can you give me little info about it or let me know about how to generate javadocs and see it for myself. Thanks, Nutan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2036301&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 14:42:54
|
Bugs item #2033470, was opened at 2008-07-31 00:31 Message generated for change (Comment added) made by jhlinder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API >Group: v0.1.0 (fixed in) >Status: Closed Resolution: Fixed Priority: 6 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Iterator/Iterable inconsistencies Initial Comment: GitStatusResponse has methods to get iterators over lists of Files. Most have been updated to return Iterable's but some are still returning Iterator's GitStatusResponse().getNewFilesToCommitIterarator() for example returns and Iterator. ---------------------------------------------------------------------- >Comment By: James H. Linder (jhlinder) Date: 2008-08-03 10:42 Message: Logged In: YES user_id=1099750 Originator: NO Confirming fixed. Marking closed. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 03:54 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:49 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 07:54:57
|
Bugs item #2033470, was opened at 2008-07-31 00:31 Message generated for change (Comment added) made by dhindsg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: None Status: Open Resolution: Fixed Priority: 6 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Iterator/Iterable inconsistencies Initial Comment: GitStatusResponse has methods to get iterators over lists of Files. Most have been updated to return Iterable's but some are still returning Iterator's GitStatusResponse().getNewFilesToCommitIterarator() for example returns and Iterator. ---------------------------------------------------------------------- >Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 03:54 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:49 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 |
From: SourceForge.net <no...@so...> - 2008-08-03 06:49:25
|
Bugs item #2033470, was opened at 2008-07-31 00:31 Message generated for change (Comment added) made by dhindsg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Commands API Group: None Status: Open >Resolution: Fixed Priority: 6 Private: No Submitted By: Patrick Winters (pcw216) Assigned to: Gurdeep Dhindsa (dhindsg) Summary: GitStatusResponse Iterator/Iterable inconsistencies Initial Comment: GitStatusResponse has methods to get iterators over lists of Files. Most have been updated to return Iterable's but some are still returning Iterator's GitStatusResponse().getNewFilesToCommitIterarator() for example returns and Iterator. ---------------------------------------------------------------------- >Comment By: Gurdeep Dhindsa (dhindsg) Date: 2008-08-03 02:49 Message: Logged In: YES user_id=2143686 Originator: NO GitStatusResponse().getNewFilesToCommitIterarator() is fixed now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1089899&aid=2033470&group_id=233450 |